inherit custom fields from parent projects - #262
Merged
Conversation
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
1 participant
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.
A project's custom fields now resolve down a chain: a vault-wide list in settings, then each ancestor project, then the project's own, with the nearest declaration of a field winning. A sub-project can rename, retype, or hide a field it inherits, or merge a duplicate it already defines into the inherited one.
Custom fields were the only per-project setting with no fallback, so a sub-project started empty and people redefined a parent's field in each child. Since field ids are generated per project, a subtree view then showed one column per copy instead of one column (#255).