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

Find a mechanism to enforce Metadata dependencies #23

Closed
andreafioraldi opened this issue Mar 5, 2021 · 2 comments
Closed

Find a mechanism to enforce Metadata dependencies #23

andreafioraldi opened this issue Mar 5, 2021 · 2 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@andreafioraldi
Copy link
Member

At the current state, we don't have any mechanism to enforce the presence of some testcase or state metadata apart from returning errors at runtime when one component that needs such metadata want to use it without success.

Can we enforce this earlier in the code, e.g. when the component is created? Or even at compile time maybe?

@andreafioraldi andreafioraldi added enhancement New feature or request question Further information is requested labels Mar 5, 2021
@evanrichter
Copy link
Collaborator

the presence of a testcase could be done at compile time perhaps with include_bytes!("../corpus/testcase1") but then compile-time and runtime could potentially diverge if that file changes or disappears

@domenukk
Copy link
Member

Feedbackstate has been refactored so this isn't really needed anymore, I think. Closing

@tokatoka tokatoka mentioned this issue Jun 3, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants