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
{{ message }}
This repository has been archived by the owner on Oct 6, 2020. It is now read-only.
This will make our interfaces take similar objects to specify similar concepts. E.g. specifying a fully-formed module as 'mod1.mod2.mod3.attr' instead of ['mod1', 'mod2', 'mod3', 'attr'].
The text was updated successfully, but these errors were encountered:
This should also include ensuring that fully-formed module paths are being passed. This will probably require a Namespace to be passed in when comparing modules and attributes.
Subclasses that implement
BadNameAttributeUseLinter
currently must specify:To migrate toward our new "module path" concept we should use module path strings instead of lists, e.g.
This will make our interfaces take similar objects to specify similar concepts. E.g. specifying a fully-formed module as
'mod1.mod2.mod3.attr'
instead of['mod1', 'mod2', 'mod3', 'attr']
.The text was updated successfully, but these errors were encountered: