[FEATURE] Api prefix #16
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
olavoasantos
added a commit
that referenced
this pull request
Aug 31, 2018
* refactored response files into separate files * adds the hability to define custom routes through the faux object (#14) * added api.prefix to the config and added prefix to routes (#16) * added relationship routes * added relationship routes (#17) * removed unecessary Faux.js file * removed test file * removed test file * fixed unparsed id on hasMany delete route
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.
Description
Currently, the app registers all routes without prefixes, yielding in endpoints such as
localhost:3000/users. For further customization, a configuration option should be added which sets a prefix to all endpoints.Solution
Defined
api.prefixto the configurations.Proposed API
Issue
Resolves #6
Release