API overhaul #392
Merged
API overhaul #392
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
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 brings a massive overhaul of Portainer API.
The package structure has been heavily inspired by @benbjohnson 's article on standard package layout:
https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1#.y32rva25k
The API endpoints have been updated to be located under:
/api/(e.g./api/users,/api/docker...)Overall, I think that it also improves the readability of the API code. It also brings a more modular architecture and future features should be easier to implement now that it has a proper structure.