-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Add the ability to tag & filters out fixtures #1043
Comments
It's an idea, but I'm a bit concerned about the complexity of this feature while I think it would be a lot easier with #998. That said I think it's somewhat doable at the moment with a faker provider -> you can pass all the fluids to it and then filter them out (but relying on the object state instead of alice's tags) |
🤔 Hmm, but how could the faker provider be aware of the fluids populated by Alice? |
I don't remember if |
No actually, as in the examples above, it'll pass a single random fluid instance. |
👍 |
Given the following fixtures:
I'd like to be able to filter out the fluids used to generate a circuit when using
@Fluid *
, as some can not be used on a primary circuit (and the model would throw a domain exception).An idea would be to add the ability to "tag" fixtures as well as filtering using a flag. Something like:
When used in a fixture name,
tags
allows to add tags to it.When used in a property/call argument/…, it allows to filter out the available fixtures for a pattern.
Note: It cannot be workaround by changing the fixture name (for instance
NonUsableFluidInPrimaryCircuit 02
) because I need the names to be formed the same way to reference them. Hence the suggestion to add something like tag capabilities (which would be more flexible as well).What do you think?
The text was updated successfully, but these errors were encountered: