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
Currently, all nested packages are accessible by any other package. We may want to reconsider this model so that nested packages are not "exported" by default, unless explicitly requested by the parent package:
This would allow those who depend on foo to be able to also access bar, otherwise any access to or dependency on bar would be a violation. If we want to export a subset of bar to the rest of the world, we would use aliasing:
We've briefly described a project where packages could put more constraints on incoming edges (in the dependency graph).
@thegedge sees two possibilities for those constraints: a whitelist option or a blacklist option (not both). In this case, we would whitelist the parent package in the nested package, which means any other package would be a violation.
The text was updated successfully, but these errors were encountered:
Currently, all nested packages are accessible by any other package. We may want to reconsider this model so that nested packages are not "exported" by default, unless explicitly requested by the parent package:
This would allow those who depend on
foo
to be able to also accessbar
, otherwise any access to or dependency onbar
would be a violation. If we want to export a subset ofbar
to the rest of the world, we would use aliasing:We've briefly described a project where packages could put more constraints on incoming edges (in the dependency graph).
@thegedge sees two possibilities for those constraints: a whitelist option or a blacklist option (not both). In this case, we would whitelist the parent package in the nested package, which means any other package would be a violation.
The text was updated successfully, but these errors were encountered: