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
If you have the phoenix.new task installed as a mix archive, you cannnot run mix phoenix.new from the installer project and have the local project's task take precedent. The only solution is to remove the archive. The ideal fix seems to have the current mix project tasks take precedent over mix archive tasks.
The text was updated successfully, but these errors were encountered:
I don't think we should do this based on two things:
If the current project is compiled the task will be used from the project, but if not compiled it will be used from the archive. This behaviour would likely be weird and unexpected for users.
If a module the task calls is accidentally deleted/renamed the bug will be hidden until the archive is deleted because the module still exists in the archive.
Example:
If you have the
phoenix.new
task installed as a mix archive, you cannnot runmix phoenix.new
from the installer project and have the local project's task take precedent. The only solution is to remove the archive. The ideal fix seems to have the current mix project tasks take precedent over mix archive tasks.The text was updated successfully, but these errors were encountered: