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

Unify filtering and validation logic #10

Open
andyward opened this issue May 7, 2024 · 0 comments
Open

Unify filtering and validation logic #10

andyward opened this issue May 7, 2024 · 0 comments

Comments

@andyward
Copy link
Member

andyward commented May 7, 2024

For some facets we have separate code paths for applying a filter to a model query (i.e. for querying/selection - typically used in applicability), and validating the elements (used by requirements). While there are reasons for the split (e.g. when verifying we want very detailed information on the failure reasons), we need to avoid subtle differences in implementations. As such we want to be re-using as much of the boolean logic as possible across selection and verification.

Generally speaking we want to be re-using the logic in Extensions helpers

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

No branches or pull requests

1 participant