Skip to content

Conversation

@spicattutti
Copy link
Contributor

Adds to #128. Now consumers don't have to select the image within the flag using potentially unsafe selectors (that might break over time) but can use a constant. Sharpens namings on exposed classes: classes.flag becomes flagContainer, to express that the span around the img is targeted

BEFORE AFTER
image image

Adds to !128. Now consumers don't have to select the image within the flag using potentially unsafe selectors (that might break over time) but can use a constant. Sharpens namings on exposed classes: `classes.flag` becomes `flagContainer`, to express that the span around the img is targeted
@spicattutti
Copy link
Contributor Author

sorry by providing the solution in 2 chunks.
When integrating the lib change, I realized I did not fully solve the problem described in #116

@viclafouch
Copy link
Owner

sorry by providing the solution in 2 chunks. When integrating the lib change, I realized I did not fully solve the problem described in #116

No worries, thanks for your work ;)

@viclafouch viclafouch merged commit a7b6839 into viclafouch:master Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants