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
Right now, if you want to, let's say, use the react template you can only use a single one (the one specified in scaffold/src folder), but makes sense that we could have more than one, for example one with JavaScript and another one with TypeScript.
This could be supported by adding a new parameter to the init command (this also opens the possibility of the CLI asking you interactively what template do you want if you do not specify one specific)
oc init myoc oc-template-react --> default oc-template-react template located on src folder oc init myoc oc-template-react --type ts --> oc-template-react typescript template located on ts folder
This might be a little verbose, so I was thinking we could allow not having to add the oc-template (does the "legacy template warning" still apply here?) to something like this:
oc init myoc react --> default oc-template-react template located on src folder oc init myoc react --type ts --> oc-template-react typescript template located on ts folder
And since the names don't mean anymore a specific library outside, the type parameter could be moved to part of the name like
oc init myoc react --> default oc-template-react template located on src folder oc init myoc react@ts --> oc-template-react typescript template located on ts folder
The text was updated successfully, but these errors were encountered:
It could also be nice to be able to reuse the template and the compiler, but specify a different scaffold/src path, in case you want to customise the final component that is generated, without having to fork all the helpers that come with a template, or the entire template monorepo for that matter.
Right now, if you want to, let's say, use the react template you can only use a single one (the one specified in
scaffold/src
folder), but makes sense that we could have more than one, for example one with JavaScript and another one with TypeScript.This could be supported by adding a new parameter to the init command (this also opens the possibility of the CLI asking you interactively what template do you want if you do not specify one specific)
oc init myoc oc-template-react
--> default oc-template-react template located onsrc
folderoc init myoc oc-template-react --type ts
--> oc-template-react typescript template located onts
folderThis might be a little verbose, so I was thinking we could allow not having to add the
oc-template
(does the "legacy template warning" still apply here?) to something like this:oc init myoc react
--> default oc-template-react template located onsrc
folderoc init myoc react --type ts
--> oc-template-react typescript template located onts
folderAnd since the names don't mean anymore a specific library outside, the type parameter could be moved to part of the name like
oc init myoc react
--> default oc-template-react template located onsrc
folderoc init myoc react@ts
--> oc-template-react typescript template located onts
folderThe text was updated successfully, but these errors were encountered: