Module name conflict interfering with package updating

[ianmackenzie]

Both ianmackenzie/elm-units and gampleman/elm-visualization define a Force module (for force the physical quantity and force-directed graphs respectively). This is now preventing @gampleman from easily updating elm-visualization to use ianmackenzie/elm-geometry 3.x, since elm-geometry 3.x uses elm-units throughout its API (so that any package that uses elm-geometry directly also has to use elm-units directly).

This in turn has caused problems with people trying to use both elm-geometry and elm-visualization within the same app (at least for @supermario, and perhaps others), since attempting to use the current version of each package causes dependency conflicts.

The Force module name conflict is an additional data point for #1625, but I believe this is the first time that it has become a problem for a package instead of an app. This makes the problem more difficult to work around, since neither package can simply rename the Force module without a breaking API change.

The current proposed workaround is to create a prefixed version of the elm-units package that re-exposes all elm-units types via aliases in modules such as Units.Force, and have functions in those modules that simply redirect to the corresponding elm-units functions.

[github-actions]

Thanks for reporting this! To set expectations:

• Issues are reviewed in batches, so it can take some time to get a response.
• Ask questions a community forum. You will get an answer quicker that way!
• If you experience something similar, open a new issue. We like duplicates.

Finally, please be patient with the core team. They are trying their best with limited resources.