We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
useId
We need to document the useId api.
@n8sabes - do you think it's feasible to throw a quick doc (using chatgpt based on #2468) for this API ?
If you don't have time that's cool, but you're the obvious first person as you're the great magician who implemented it :)
At any case, thanks! 🙏
The text was updated successfully, but these errors were encountered:
@n8sabes if for you it's ok I will create the doc section for this. Let me know.
Sorry, something went wrong.
@gioboa, Thanks for prodding me on this issue. I have something written up and will submit a PR this weekend. I was thinking about putting it just after Component>Overview just after Getting hold of DOM element -- what do you guys think?
After ref description sounds good to me
Add useId() to docs
722709a
Add useId() to docs, closing issue QwikDev#4120.
n8sabes
No branches or pull requests
Suggestion
We need to document the
useId
api.@n8sabes - do you think it's feasible to throw a quick doc (using chatgpt based on #2468) for this API ?
If you don't have time that's cool, but you're the obvious first person as you're the great magician who implemented it :)
At any case, thanks! 🙏
The text was updated successfully, but these errors were encountered: