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 was archived by the owner on Jan 29, 2020. It is now read-only.
As the subject says, unlike most methods in that class, getTraitNames() does not call scan() before checking available data. This means that if you call getTraitNames() or getTraits() as the first action on a newly-instantiated ClassScanner, you won't get any traits, depsite there being traits.
Unless someone confirms that this is intended behaviour and isn't actually a bug, I'll happily submit a PR to fix the issue.
The text was updated successfully, but these errors were encountered:
As the subject says, unlike most methods in that class,
getTraitNames()
does not callscan()
before checking available data. This means that if you callgetTraitNames()
orgetTraits()
as the first action on a newly-instantiatedClassScanner
, you won't get any traits, depsite there being traits.Unless someone confirms that this is intended behaviour and isn't actually a bug, I'll happily submit a PR to fix the issue.
The text was updated successfully, but these errors were encountered: