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'm starting to use your plugin to work on a multi language monorepo with rust, react and web assembly and its help a lot so thanks for this nice plugin.
I've a question about the name of the project in the nx configuration files. You chose to use snake case but most (all ?) of the plugin written by the @nrwl/nx team are using snake case with hyphen instead of underscore. I'm not really here to debate about the best way to name variable but it add a bit of inconsistency in the files of the monorepo.
So my request would be to change this behaviour to be the same as for @nrwl/nx.
I won't mind doing it myself in a pull request if you are willing to accept this change.
Regards,
Guillaume
The text was updated successfully, but these errors were encountered:
Hey @Arcahub, unfortunately I've been neglecting this poor project. >_< My intention is to fix this so that the plugin supports both kebab-case and snake_case projects without any issues. Unfortunately I haven't had the time to look into it yet. I will have a few days off next week, so I'll do my best to tackle it then. But if you'd like to take a crack at it in the meantime, please feel free!
Hello,
I'm starting to use your plugin to work on a multi language monorepo with rust, react and web assembly and its help a lot so thanks for this nice plugin.
I've a question about the name of the project in the nx configuration files. You chose to use snake case but most (all ?) of the plugin written by the
@nrwl/nx
team are using snake case with hyphen instead of underscore. I'm not really here to debate about the best way to name variable but it add a bit of inconsistency in the files of the monorepo.So my request would be to change this behaviour to be the same as for
@nrwl/nx
.I won't mind doing it myself in a pull request if you are willing to accept this change.
Regards,
Guillaume
The text was updated successfully, but these errors were encountered: