v3 HTTP API development #292
Merged
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
edaniszewski
added a commit
that referenced
this pull request
Mar 27, 2020
* update plugin loading, do not purge plugins once loaded * update plugin management and active/inactive tracking * add sync write transactions to cache * fix bug with reading tags, use util to get plugin from device, exception handling * update reading response scheme
edaniszewski
added a commit
that referenced
this pull request
Mar 30, 2020
* update plugin loading, do not purge plugins once loaded * update plugin management and active/inactive tracking * add sync write transactions to cache * fix bug with reading tags, use util to get plugin from device, exception handling * update reading response scheme
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.
This PR continues the development of the v3 HTTP API. It fixes various bugs and updates the response scheme to align it more with the spec. There is more work to be done here, but this is a big step forward in API consistency and functionality.
Related: