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 Aug 9, 2018. It is now read-only.
I'm looking to start adding SVGs that serve the same purpose at other SVGs in edna. Using the current scheme, they would have the same names. Any thoughts on a better naming convention?
The text was updated successfully, but these errors were encountered:
Naming based on their visual appearance seems like a better idea. It would involve less clashing, and naming of these files doesn't feel like it needs a purpose-based name(like transport-prev). Describing the display can be more lengthy too, so these might get ugly in CSS.
We may want to do this as we implement GruntIcon 2.0 ( #45 ). Will need to look into inline SVGs a bit more. As we transition over these specific names might cause headaches when we bring these into the template.
I'm looking to start adding SVGs that serve the same purpose at other SVGs in edna. Using the current scheme, they would have the same names. Any thoughts on a better naming convention?
The text was updated successfully, but these errors were encountered: