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
Report when it looks like parts of the projects are structured like an MVC construct, separated into multiple files. So if you have multiples files named Xyz.<name> where at least two of the names is Model, View, Update, ..., then they should be reported.
Someone to implement it (I can provide help and guidance)
A good rule name. NoMVCSeparation, NoOverSeparatingModules?
What names should be reported.
Model, View, Update, Subscriptions. Types? Maybe also Msg and/or Init? Let me know what you have seen used!
Lamdera needs a Types.elm module at the root of the project, but as long as users don't create another module with a "smelly" name, it should be fine.
The text was updated successfully, but these errors were encountered:
What problems does it solve:
The official guide explains the problem quite well.
What the rule should do:
Report when it looks like parts of the projects are structured like an MVC construct, separated into multiple files. So if you have multiples files named
Xyz.<name>
where at least two of the names is Model, View, Update, ..., then they should be reported.Example of things the rule would report:
The
^^^^
indicate where I think the error should appear.The same issue should also be reported if the module names are not prefixed.
The contents of the module and what it exposes should not matter.
Example of things the rule would not report:
No apparent over-separation from the module name
Only a single oddly named module per "component", which likely indicates an odd naming for the module, but not an over-separation problem.
When (not) to enable this rule:
This rule will only be useful for applications.
I am looking for:
Model
,View
,Update
,Subscriptions
.Types
? Maybe alsoMsg
and/orInit
? Let me know what you have seen used!Lamdera needs a
Types.elm
module at the root of the project, but as long as users don't create another module with a "smelly" name, it should be fine.The text was updated successfully, but these errors were encountered: