> should also consider making another push to e...
# development
h
should also consider making another push to enable it by default.
what is the story with using the interactive UI at the same time as V1? That’s the biggest issue afaict. We default to
--v1 --v2
h
I haven't tried it at all since the recent change to the library. I don't think v1 exercises the code path it gets activated in?
h
NB that you can run
./pants --v1 --v2 lint
with V1 and V2 linters enabled at the same time. That’s I think the biggest thing we need to make sure works if we’re to enable
--v2-ui
by default
w
it should be fine… it will render for the relevant period, and then go away.