sparksp / elm-review-imports

elm-review rule to enforce consistent import aliases

https://package.elm-lang.org/packages/sparksp/elm-review-imports/latest/

sparksp/elm-review-imports Issues

Forbid aliases for certain imports
Updated 3 months ago1
Shadowing when aliasing a type with the same name
Updated a year ago2
False negative on `Json.Decode` when `Json.Decode.Extra` import is also present
Updated a year ago
Shadowing issue with record pattern matching for NoModuleOnExposedNames
Updated a year ago
Applying the fix doesn't always update instances of Module.Constructor
Closed 3 years ago3
NoModuleOnExposedName fix can introduce name collision
Updated a year ago6
Alternate way to configure consistent alias rule
Updated 4 years ago2
Discussion: Allow multiple aliases?
Updated 4 years ago4
Check for default exposes
Closed 4 years ago1
Do not allow exposed names to be qualified
Closed 4 years ago1
Enforce use of an alias when one is known
Closed 4 years ago
Enforce consistency for every alias
Updated 4 years ago
Enforce preferred names
Closed 4 years ago
Collision detection with preferred aliases
Updated 3 years ago1
Ensure Consistent Aliases
Updated 4 years ago