Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's the use case for this? #4

Closed
impressivewebs opened this issue Mar 15, 2023 · 2 comments
Closed

What's the use case for this? #4

impressivewebs opened this issue Mar 15, 2023 · 2 comments

Comments

@impressivewebs
Copy link

Looks interesting, but I'm not sure exactly what this would be used for. What is the significance of adding the prefix "current-" to meta tag names? For example, why not have the library access all meta tags regardless of the use of "current-"?

@marcoroth
Copy link
Owner

Hey @impressivewebs, the reason for that is that you can also have other <meta> tags in your head which aren't meant to be accessed that way. The current- prefix is more meant as an opt-in mechanism, so that you explicitly need to name them that way.

But that makes we wonder if we should allow a custom prefix, which one could set to "" (empty string) if they'd want to access any <meta> element.

@marcoroth
Copy link
Owner

Going to close this one for now, but please feel free to reopen! 🙌🏼

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

No branches or pull requests

2 participants