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
Thank you for your issue report! Unfortunately, this is a known problem. The issue is that currently there is no way to distinguish if a mutation is possible, other than based on syntax. And if something goes wrong, we have no rollback process implemented (#14). As a temporary fix, you could always ignore the file to be mutated with the following stryker4s.conf:
@hugo-vrijswijk
So my understanding is that nonEmty/isEmpty is aimed at collections, is that right?
If so, then can we also check the type before applying this mutation? Not sure how easy that is, but sounds possible, wdyt?
It should be possible, yes! Likely either by using SemanticDB or through an experiment with TASTY. I tried a little experiment with SemanticDB a while back, but didn't get as far as I would've liked.
Ideally, we'd do both (type check and compile rollback), but that is likely a little further down the line.
Summary
I have an object with method named
nonEmpty
, likeand call
QueryParams.nonEmpty
is mutated toQueryParams.isEmpty
which of course doesn't compile
Stryker4s config
default
Stryker4s environment
Your Environment
The text was updated successfully, but these errors were encountered: