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
I can't identify here any of these testing libraries. It would be great for me if I could add some condition using a 'where' keyword:
buildozer \
'set testing_only 1' \
'where ("//java/junit" in deps and testing_only != 1)'$(find -L ~/my_project -name BUILD | sed"s/\/BUILD/:%java_library/")
The semantics of where is basically to match the entire build rule and, if it doesn't match the condition, then skip it from the atomic mutation.
Multiple 'where' operators would be either 'and'-ed or a parse error.
This would make a ton of refactors much easier instead of doing constant git manipulations to have better specificity especially for BUILD files with many tests.
The text was updated successfully, but these errors were encountered:
I think the most powerful would be a combination of the conditional and the find, so that it would be possible to write a single buildozer script that would work on both *ix and windows. That is, do not rely on xargs or find or sed.
Say I need to set testing_only to 1 for all java testing libraries. These libraries are identified by having a //java/junit dependency
I can't identify here any of these testing libraries. It would be great for me if I could add some condition using a 'where' keyword:
The semantics of where is basically to match the entire build rule and, if it doesn't match the condition, then skip it from the atomic mutation.
Multiple 'where' operators would be either 'and'-ed or a parse error.
This would make a ton of refactors much easier instead of doing constant git manipulations to have better specificity especially for BUILD files with many tests.
The text was updated successfully, but these errors were encountered: