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
Since I make a bazillion plugins, I created a really cool template that automates a lot of the grunt work, however when you do a tns create --template <pluginTemplate> - TNS totally messes up my all new tns plugin project and really destroys it's usability.
Can we make it so that if I have a flag in the template package.json like {"cleanTemplate": "true"} that the tns will not start messing with things it doesn't understand. ;-) Or if you MUST install all that crap; please put it into the "demo" folder (if the demo folder exists in the template); as that is where the actual demo project will resides. I have no problem automating the install of the demo folder; but man it is a serious pita to work around tns's attempt to destroy my cool new plugin...
The text was updated successfully, but these errors were encountered:
Since I make a bazillion plugins, I created a really cool template that automates a lot of the grunt work, however when you do a
tns create --template <pluginTemplate>
- TNS totally messes up my all new tns plugin project and really destroys it's usability.Can we make it so that if I have a flag in the template package.json like {"cleanTemplate": "true"} that the tns will not start messing with things it doesn't understand. ;-) Or if you MUST install all that crap; please put it into the "demo" folder (if the demo folder exists in the template); as that is where the actual demo project will resides. I have no problem automating the install of the demo folder; but man it is a serious pita to work around tns's attempt to destroy my cool new plugin...
The text was updated successfully, but these errors were encountered: