Skip to content
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

Allow SoftSignals to have and propagate metadata #363

Merged
merged 4 commits into from
Jun 14, 2024

Conversation

DiamondJoseph
Copy link
Contributor

Closes #356

@DiamondJoseph DiamondJoseph force-pushed the 356_signal_metadata branch 2 times, most recently from 097fb5a to d6399a0 Compare June 5, 2024 07:46
@coretl
Copy link
Collaborator

coretl commented Jun 5, 2024

when test is added...

Comment on lines 152 to 153
units: Optional[str] = None,
precision: Optional[int] = None,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or SoftSignalBackend can take kwargs of other fields to pass as configuration.
e.g. units, precision, choices, limits

@DiamondJoseph DiamondJoseph force-pushed the 356_signal_metadata branch 2 times, most recently from 5b5d767 to 110ffad Compare June 13, 2024 08:13
@DiamondJoseph
Copy link
Contributor Author

Replaced by #367

@DiamondJoseph
Copy link
Contributor Author

Wrong branch

@DiamondJoseph DiamondJoseph reopened this Jun 14, 2024
@DiamondJoseph DiamondJoseph merged commit e4ab7d6 into main Jun 14, 2024
18 checks passed
@DiamondJoseph DiamondJoseph deleted the 356_signal_metadata branch June 14, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow SoftSignals metadata (units, limits etc.)
2 participants