koopjs / koop-core Goto Github PK
View Code? Open in Web Editor NEWCore library for KoopJS (deprecated)
License: Other
Core library for KoopJS (deprecated)
License: Other
Koop-core should JSON.parse
any incoming req.query
that arrive as JSON strings.
It would be nice to not have to fork a provider if you wanted to append or transform data. For example, if my provider is the AGOL provider and I want to take a layer's results from AGOL on the fly and enrich the data (change some values or add additional fields) it would nice to have a place in the koop layer that exposes the results of the provider with a way for you to mutate it before its sent out vs having to extend the provider for every use case.
Ideally there would be an option for the winnow query to be run against the transformed dataset to apply the query against the transformed data (to filter it further)
I'm trying to send geo data to arcgis utilizing my own custom Koop provider, however even though the resulting query recognizes the z value of a POINTZ and prints it as such in the geometry, the "hasZ" field of the overall query is still "false". I've looked around the docs but I have not found any way to manually change it to "true" either. Is there a way to fix this issue?
3.3.3
to 3.3.4
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
gh-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
b7d2b3a
3.3.4
bff3b7b
docs(changelog): updates for 3.3.4 release
0c5c8b3
Fix unhandled invalid repository URL error (#83)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These updates are currently rate-limited. Click on a checkbox below to force their creation now.
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
.github/workflows/node.js.yml
actions/checkout v3
actions/setup-node v3
package.json
@hapi/joi ^17.1.0
@koopjs/cache-memory ^2.0.2
@koopjs/logger ^2.0.6
@koopjs/output-geoservices ^3.1.6
body-parser ^1.19.0
chalk ^4.0.0
compression ^1.7.4
config ^3.3.1
cors ^2.8.5
easy-table ^1.1.1
ejs ^3.1.2
express ^4.17.1
featureserver ^4.0.1
koop-localfs ^1.1.2
lodash ^4.17.15
gh-release ^4.0.0
husky ^4.2.5
lint-staged ^10.1.7
mocha ^10.2.0
should ^13.2.3
should-sinon 0.0.6
sinon ^9.0.2
standard ^14.3.1
supertest ^4.0.2
Currently, output-plugin routes are bound before a provider's routes. Thus, any routing conflicts default to the output-plugin routes. This limits the ability of a provider to add custom routes to supersede a output-plugin route. Therefore, the binding order should be switched.
Branch | Build failing π¨ |
---|---|
Dependency | supertest |
Current Version | 3.2.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
supertest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
#509 - Fix #486, bug in _assertBody, switch to deepStrictEqual
(thanks @mikelax)
#510 - Refactor test files to use const/let (thanks @rimiti)
The new version differs by 10 commits.
e910e85
chore: Prepare for v3.3.0 release.
bd864de
Merge pull request #511 from visionmedia/bugfix-486-equal
101fbf5
Merge branch 'master' into bugfix-486-equal
04230bb
Merge pull request #510 from visionmedia/refact-const-let
510a7ae
bugfix: 486 Change method to use deepStrictEqual. (#509)
913150d
chore(.editorconfig) [*.md] block removed
82e0828
refact(test/supertest.js) vars replaced by const and let
5443136
chore(.editorconfig) configuration file created
7233ba6
chore(.eslintrc) parserOptions option added to use es6
322ebf6
bugfix: 486 Change method to use deepStrictEqual.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Has anyone tested AWS API Gateways with Koop and Lambda. Seems serverless might actually be a reality at some point. This would be extremely powerful for multiple reasons, one is it would allow you to scale unique authentication per service or per group of services.
I am going to do some work in this space and report back what I have found.
It would be helpful to allow provider plugins to use a pass a Stream.Readable
instead of GeoJSON to the output plugins.
This would allow the output plugins to begin processing data as soon as it's available instead of having to wait for the entire result of a request to be loaded into memory beforehand.
Branch | Build failing π¨ |
---|---|
Dependency |
koop-output-geoservices
|
Current Version | 1.2.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
koop-output-geoservices is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
###Added
authenticationSpecification
(if exists) in the rest/info
handler and pass data to FeatureServerrest/generateToken
and pass on to associated handler which in turn calls model's authenticate
functionThe new version differs by 4 commits.
16169d1
:package: 1.3.0
c25acc5
Merge branch 'master' of https://github.com/koopjs/koop-output-geoservices
02e4152
Bump featureserver dependency.
1e6bcea
Pass authentication info from provider to FeatureServer (#9)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
In generic plugin registration an error is currently thrown if the plugin name is defined.
const name = Plugin.name || Plugin.plugin_name
if (name) throw new Error('Plugin is missing name')
Probably should be the opposite of that?
Branch | Build failing π¨ |
---|---|
Dependency |
sinon
|
Current Version | 5.0.8 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 5 commits.
86b930c
Update docs/changelog.md and set new release id in docs/_config.yml
033aa60
Add release documentation for v5.0.9
3321085
5.0.9
9f321d5
Update History.md and AUTHORS for new release
e862196
Upgrade @std/esm
to esm
.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
The Esri python API passes in 'True'
and 'False'
for boolean parameters. Can you fix this to handle this variation in case?
koop-core/src/middleware/index.js
Line 34 in 99d01c4
Branch | Build failing π¨ |
---|---|
Dependency | mocha |
Current Version | 3.3.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As mocha is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.
This week's highlights:
allowUncaught
added to commandline as --allow-uncaught
(and bugfixed)--no-warnings
and --trace-warnings
flags (@sonicdoe)The new version differs by 9 commits0.
7554b31
Add Changelog for v3.4.0
9f7f7ed
Add --trace-warnings
flag
92561c8
Add --no-warnings
flag
ceee976
lint test/integration/fixtures/simple-reporter.js
dcfc094
Revert "use semistandard
directly"
93392dd
no special case for macOS running Karma locally
4d1d91d
--allow-uncaught cli option
fb1e083
fix allowUncaught in browser
4ed3fc5
Add license report and scan status
false
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
I tried to register an output with routes with uppercase request methods like GET
but it failed. Turning the request method back to the lowercase worked.
It should accept both lowercase and uppercase for the route request method.
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.yml
If youβre interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines
key in any package.json
file, the .nvmrc
file, and the .travis.yml
file, if present.
engines
was only updated if it defined a single version, not a range..nvmrc
was updated to Node.js 10.travis.yml
was only changed if there was a root-level node_js
that didnβt already include Node.js 10, such as node
or lts/*
. In this case, the new version was appended to the list. We didnβt touch job or matrix configurations because these tend to be quite specific and complex, and itβs difficult to infer what the intentions were.For many simpler .travis.yml
configurations, this PR should suffice as-is, but depending on what youβre doing it may require additional work or may not be applicable at all. Weβre also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, Iβm a humble robot and wonβt feel rejected π€
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
π¨ Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! π ππ¨ π
Find out how to migrate to Snyk at greenkeeper.io
2.0.4
to 2.0.5
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@koopjs/logger is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 14 commits.
c9f6a7a
:package: 2.0.5
36db96f
Delete locks introduced by automated update.
ba5585a
Update dependencies.
7a5892f
Update for standard.js.
75caf73
Merge pull request #7 from koopjs/greenkeeper/standard-13.0.1
975c18b
Merge pull request #8 from koopjs/dependabot/npm_and_yarn/lodash-4.17.15
31de51a
:arrow_up: Bump lodash from 4.17.4 to 4.17.15
717b1e9
chore(package): update standard to version 13.0.1
dce77f5
Scope the require tp @koopjs.
6417b5d
Fix install command in README
29158bd
Merge pull request #6 from koopjs/greenkeeper/standard-12.0.0
9b1d9a1
Merge pull request #4 from koopjs/greenkeeper/winston-3.0.0
74e4e90
chore(package): update standard to version 12.0.0
7b4549a
fix(package): update winston to version 3.0.0
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
previously I used cache.append with key = result of createKey now i think I must use createKey::data.
trying to avoid trial and error process ...
6.2.1
to 6.2.2
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
EVENT_RUN_END
events upon uncaught exception (@juergba)html
reporter (browser) (@pec9399)The new version differs by 12 commits.
843a322
6.2.2
aec8b02
update CHANGELOG for v6.2.2 [ci skip]
7a8b95a
npm audit fixes
cebddf2
Improve reporter documentation for mocha in browser. (#4026)
3f7b987
uncaughtException: report more than one exception per test (#4033)
ee82d38
modify alt text of image from Backers to Sponsors inside Sponsors section in Readme (#4046)
e9c036c
special-case parsing of "require" in unparseNodeArgs(); closes #4035 (#4063)
954cf0b
Fix HTMLCollection iteration to make unhide function work as expected (#4051)
816dc27
uncaughtException: fix double EVENT_RUN_END events (#4025)
9650d3f
add OpenJS Foundation logo to website (#4008)
f04b81d
Adopt the OpenJSF Code of Conduct (#3971)
aca8895
Add link checking to docs build step (#3972)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
The logic at src/index.js:334 seems to be backwards. When creating a plugin as a class or function, the name
property is a read-only property from the Function
object. In this scenario, we will never get to the plugin_name
property. This causes an issue when uglifying code, because the value of Plugin.name
becomes the new unrecognizable name given to the function in the uglification process. If the logic was instead: Plugin.plugin_name || Plugin.name
, the name
property would serve as a fail-safe and the plugin_name
property would act as an override.
If this is not the intended use of plugin_name
, then a different solution needs to be explored to resolve the bug introduced by uglifying logic.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.