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 Jul 20, 2018. It is now read-only.
If a theme is registering and/or enqueuing a custom js or css asset, we should ensure that a unique slug is used. A relatively simple way to do so would be to check the slug for the presence of an _ or - character, which would indicate at least some sort of namespacing.
Anything w/o one of those in the slug would be assumed to be using a generic name.
The text was updated successfully, but these errors were encountered:
If a theme is registering and/or enqueuing a custom js or css asset, we should ensure that a unique slug is used. A relatively simple way to do so would be to check the slug for the presence of an
_
or-
character, which would indicate at least some sort of namespacing.Anything w/o one of those in the slug would be assumed to be using a generic name.
The text was updated successfully, but these errors were encountered: