-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field titles #333
Merged
Merged
Field titles #333
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
aefdde4
feat: use title for fields closes #319 fixes #314
JohnCoene 388716d
feat: field titles as arguments
JohnCoene bf04c82
ci: add tests
JohnCoene 38e28af
lint: blockr 193
JohnCoene 7f9d4da
lint: block l 423
JohnCoene 6381894
revert: do not expose field titles
JohnCoene File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With multiple fields, this does not look super nice, too many parameters. I don't have a good working idea on how to parametrise fields (at least field names) from the block. If we use a single
field_names
param which can take a vector of name, this might be misleading for single field blocks.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have better idea @nbenn ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly (and sorry @JohnCoene for suggesting to revert a change you were asked to make), my proposal here would be to not expose these names as arguments for now. If we want to make such aspects customizable, I think we need to do something else.
@christophsax at one time floated the idea to also have other field-level metadata, such as a description, and I don't think it makes sense to surface all of that as block constructor arguments.