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
Currently, the template doesn't support to apply only specific addon yet, someone might use the template to add a few add-ons instead of the whole template.
For example:
mix nimble.phx.gen.template addon=credo # applying only credo addon to an existing project
mix nimble.phx.gen.template addon=wallaby # applying only wallaby addon to an existing project
The text was updated successfully, but these errors were encountered:
As the existing project's structure might differ from the original project, so it will be challenging to apply the addon to that. We can implement this one by 2 phrases
Phrase 1: Instead of applying the addon, we can render the step-by-step how to integrate the addon like a guide so the user can add it manually regardless of their existing structure.
eg: with the Oban addon
Step 1: add Oban into the mix.ex file
Step 2: Create the migration file with the following content ....
Step 3: ....
Phrase 2: Apply to any existing structure, this would be a hard task.
Currently, the template doesn't support to apply only specific addon yet, someone might use the template to add a few add-ons instead of the whole template.
For example:
The text was updated successfully, but these errors were encountered: