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
When I use tuist init command and specify a template located in a remote repository, the additional attributes specified in the Template.swift are ignored. For example:
If I initialize the project using this template located remotely, then the test parameter will not be taken into account:
tuist init -t https://github.com/path/to/template.git
Project generated at path /path/to/project.
At the same time, if I initialize the project using the same template located locally, then all parameters are taken into account:
tuist init -t localtemplate
You must provide test option. Add --test desired_value to your command.
Consider creating an issue using the following link: https://github.com/tuist/tuist/issues/new/choose
In the source code, only name and platform parameters are passed for git template.
Maybe it makes sense to parse the arguments after cloning the repository to a temporary folder so that they are taken into account for remote templates?
When I use tuist init command and specify a template located in a remote repository, the additional attributes specified in the Template.swift are ignored. For example:
If I initialize the project using this template located remotely, then the test parameter will not be taken into account:
tuist init -t https://github.com/path/to/template.git
Project generated at path /path/to/project.
At the same time, if I initialize the project using the same template located locally, then all parameters are taken into account:
tuist init -t localtemplate
You must provide test option. Add --test desired_value to your command.
Consider creating an issue using the following link: https://github.com/tuist/tuist/issues/new/choose
In the source code, only name and platform parameters are passed for git template.
Maybe it makes sense to parse the arguments after cloning the repository to a temporary folder so that they are taken into account for remote templates?
Hello 👋
It makes sense! Would you like to try to implement this? 🙏
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I use
tuist init
command and specify a template located in a remote repository, the additional attributes specified in theTemplate.swift
are ignored. For example:If I initialize the project using this template located remotely, then the
test
parameter will not be taken into account:At the same time, if I initialize the project using the same template located locally, then all parameters are taken into account:
In the source code, only
name
andplatform
parameters are passed for git template.Maybe it makes sense to parse the arguments after cloning the repository to a temporary folder so that they are taken into account for remote templates?
Beta Was this translation helpful? Give feedback.
All reactions