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
Change default generation target path of mix task mix waffle.g to "data" application.
Reasoning
Let's say i have a crawler application for example, and it consists of three subapplications: "ecto" part, "crawl" part, and "CLI" part, there is no "web" application with controllers, views and templates:
"Crawler" app and "CLI" app may fetch images from remote host or process from user input in console - two different ways of getting image data. I want to have one place to describe transformation and storing image data process, so it's obviously should be put into "data" application, because "data" applications are responsible for storing/validation, not "web" applications.
Actual behaviour (it puts generated uploader under "/lib/#{app_name}_web/uploaders/"):
Suggestion
Change default generation target path of mix task
mix waffle.g
to "data" application.Reasoning
Let's say i have a crawler application for example, and it consists of three subapplications: "ecto" part, "crawl" part, and "CLI" part, there is no "web" application with controllers, views and templates:
"Crawler" app and "CLI" app may fetch images from remote host or process from user input in console - two different ways of getting image data. I want to have one place to describe transformation and storing image data process, so it's obviously should be put into "data" application, because "data" applications are responsible for storing/validation, not "web" applications.
Actual behaviour (it puts generated uploader under
"/lib/#{app_name}_web/uploaders/"
):waffle/lib/mix/tasks/g.ex
Line 55 in 8dcaede
Example
New skeleton would look like this:
The text was updated successfully, but these errors were encountered: