Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

Field change: exposed-modules to exported-modules #158

Closed
mgold opened this issue Oct 26, 2015 · 1 comment
Closed

Field change: exposed-modules to exported-modules #158

mgold opened this issue Oct 26, 2015 · 1 comment

Comments

@mgold
Copy link

mgold commented Oct 26, 2015

Related to elm/compiler#1124, we should be more precise about the definition of exposed vs. exported. The exposed-modules field of elm-package.json should be renamed exported-modules (in a backwards compatible way). This will clarify the distinction between exporting a module for others and importing it with values exposed for your own use.

@evancz
Copy link
Contributor

evancz commented Nov 17, 2015

I kind of think this distinction is weird. It does not feel like it has a clear uniform meaning across all the things you are interested in. Overall, I'm not sure if making a subtle weird distinction is worth the confusion it'll cost in having to tell everyone the subtle weird distinction so they can remember which is which.

Anyway, point is elm-lang/elm-make#59 has discussion of this, so now there's a link and it'll be in the feed when I go to work on that stuff. I don't want to cause a side-discussion, so please do not add additional comments there. The backlink will work!

@evancz evancz closed this as completed Nov 17, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants