Repository navigation
Add FieldLabel, the Annotated display label for a field (0.2.6) - #21
Merged
Merged
Conversation
Form and table builders read a field's label from its declaration instead of each application defining its own label marker. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds
FieldLabelanddeclared_field_labelbesideAnnotationChoices:Annotatedmetadata declaring the display label of a field whose name does not read well. pyqt-reactive's editable tables (moved from OpenHCS in OpenHCS surface U3/L4) read labels through it, so applications no longer define their own label marker. Version 0.2.6.Release order for the OpenHCS U3 train: python-introspect 0.2.6 → ObjectState 1.4.0 → pyqt-reactive 0.5.0 → OpenHCS repin.
Not tagged or released; the owner releases.
🤖 Generated with Claude Code