Hi, > >I would almost prefer for this to be a question asked on startup of > >the cdk (that can be overriden). The question could explain the > >limitation and why it will exist in production and then the user can > >choose if they want to ignore and run without restrictions. > > I am conservative about asking questions during setup as it reduces the user > experience and we are not sure if the user has enough knowledge about it.
I am usually also against asking questions, but this might be the only way to get a user to at least read the question. We can write it in as many places we want, unless we literally force the user to make a choice, we will have people running into this problem. Since who read documentation, right? --Hardy
signature.asc
Description: PGP signature
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
