Feature: Store resource data under a data key#3
Open
alblandino wants to merge 2 commits into
Open
Conversation
Owner
|
Hey @jblandino! Nice to see you there mate! Would not be better to allow user specify the id if they want to? I think it is more simple and straightforward to allow the user to provide and id or let the api to auto generate one. What do you think? |
Owner
|
Will continue the discussion here: #2 |
data key
This file contains hidden or 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.
I am adding a new index called data to protect the self-generated id in case the user adds a field ID
For example, I am sending these values:
I receive and storage the values in this way:
The behavior of the module is the same, the only thing that in this case allows the user to save his own ID of his application since by default lowdb does not allow a dynamic ID