-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.2.0 #297
Merged
Merged
Release 2.2.0 #297
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix action name link => _link
- Store if a payload is skipped, valid or error. - Store the reason of the error, when a user defined validation error occurs.
remove unnecessary call to engineConfigManager.createCollection since it's already done in AbstractEngine class from kuzzle-plugin-commons add the asset history collection in the method return
Refactor to comply with the module architecture. Basically split classes of the core/ directory between plugin, model and decoder modules
Store reason of discarded payloads
- When an asset is created or updated, we saved the complete paths in asset history document.
Full path nested metadata when create/update assets
Allow to specify nested metadata
Export the base mappings for the plugin collection. This can be used to define other collection based on KDM collections.
Add an API to exports measures in CSV. Those actions allow to export the measures history of an asset or a device. The measures are exported as a CSV stream. The export process have two steps: - execute the exportMeasures action with WebSocket or HTTP POST to prepare an export and retrieve an export link - GET request to the generated export link through a tag <a href="{export-link}">Download</a> Those two steps are necessary to avoid the browser to crash when exporting a lot of data. Export link are valid for 2 minutes.
* test(asset-history): Historize asset for each measurements * fix: historize asset for each same measurement received * feat: add a timestamp property to asset history content * chore: pr comments * fix: historize asset only if asset is not null * fix: use a Map in order to keep insertion order * fix: historize metadata changes only on last asset State * fix: add metadata to last asset-history document * chore(ci): lint * feat: use mCreate for asset history instead of create * fix: async function * Update lib/modules/asset/AssetHistoryService.ts Co-authored-by: Adrien Maret <Aschen@users.noreply.github.com> * Update lib/modules/asset/AssetService.ts Co-authored-by: Adrien Maret <Aschen@users.noreply.github.com> --------- Co-authored-by: Théo Dislay <tdislay@kuzzle.io> Co-authored-by: Adrien Maret <Aschen@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2.2.0 (2023-04-17)
Bug fixes
New features
Enhancements
Others