You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for only just looking at this, going through all the old issues now.
I definitely agree that having to specify each ExactValue isn't ideal. The main downside of the function approach above is that any numeric effect will be assumed to be an ExactValue. Are there ever situations where you may have another numeric based effect?
If not we can refactor to this approach, it would be a breaking change for the frontend though
I'm not sure. At the moment, I think the only supported numerics are exact values. The other possibility, which I've just thought of, is to specify, in the tests.json file, the name of the effect class (Positive, Negative, etc.) and have an additional field for the arguments with which to initialise the class. I think that would be better, and might not necessarily need to be a breaking change.
When we set up a driver for the JSON front end, we have something like the following:
This works great for this kind of effects, but when I want to test for exact values, I have:
This is expanding as I need to add more literal values. Could we perhaps use a function instead, so I could have something like
or would that be bad?
The text was updated successfully, but these errors were encountered: