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
Empty modules are "valid" Gleam in the sense they won't block compilation, but they are useless for a package to publish because they don't do anything! I can see two scenarios for why a package might have been published with empty modules:
to stub out the package's API before it is complete.
as a mistake
The first scenario is confusing for users and will waste folks' time as they work out what parts of the API actually exist. The second scenario is an unfortunate accident that the compiler could have prevented!
I propose Gleam refuses to publish any package if it contains empty modules, and emits warnings when building a project with empty modules.
The text was updated successfully, but these errors were encountered:
I'd like one indication tho
Since I don't wan't to publish tests or anything on Hex, what's the procedure to test the publish command without any side effect ?
I didn't found it in the docs
Empty modules are "valid" Gleam in the sense they won't block compilation, but they are useless for a package to publish because they don't do anything! I can see two scenarios for why a package might have been published with empty modules:
The first scenario is confusing for users and will waste folks' time as they work out what parts of the API actually exist. The second scenario is an unfortunate accident that the compiler could have prevented!
I propose Gleam refuses to publish any package if it contains empty modules, and emits warnings when building a project with empty modules.
The text was updated successfully, but these errors were encountered: