Unique/Name Key#112
Open
willronchetti wants to merge 8 commits intomasterfrom
Open
Conversation
carlvitzthum
approved these changes
Nov 25, 2019
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
2 participants
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.
keys.rst- an overview of how the various keys work in Snovault and how it applies to FF/CGAP. This should be useful in making decisions with respect to the data modelunique_keyon the collection decorator totraversal_key. The reason being that while thetraversal_keymust be a unique key calling itunique_keyis misleading as it is different than marking an item property as auniqueKeyon the item schema.name_keyonly augments the resource path and must match thetraversal_keyif it is used.