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
Specs shouldn't use non-exported terms this way. Maybe it would help if bikeshed emit some warning (or even just some info-level log) that suggests filing an issue on the referenced spec.
The text was updated successfully, but these errors were encountered:
Oh, didn't know #1792 exists. IMO it makes more sense to warn the one who references rather than the one who is being referenced, but either way may work.
One thing I wonder is whether warnings would be too destructive as one may pass --die-on everything on CI. Probably fine given that both spec-factory and spec-prod don't use such configuration by default.
Specs shouldn't use non-exported terms this way. Maybe it would help if bikeshed emit some warning (or even just some info-level log) that suggests filing an issue on the referenced spec.
The text was updated successfully, but these errors were encountered: