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 Nov 22, 2024. It is now read-only.
TextFields and other components that have the id as a prop default to that ID being null for some reason, which is the reason of warnings in the console like:
Found 2 elements with non-unique id #null
The text was updated successfully, but these errors were encountered:
This seems to be an issue with Sapper's rendering (though I couldn't find any related open issue on their repo). This is because if I navigate to https://illright.github.io/attractions/docs/components/text-field by first going to https://illright.github.io/attractions/docs/ and then clicking on "TextField", I don't get this error. Even when going to that page directly, the null id is only present in the page source (CTRL + U), but not actually on the element if you inspect it through the DevTools.
Yeah, when I investigated, I also came to the conclusion that Sapper renders out the null-valued props and Svelte removes them afterwards. Been meaning to create an MCVE and open an issue to Sapper
TextFields and other components that have the
id
as a prop default to that ID beingnull
for some reason, which is the reason of warnings in the console like:The text was updated successfully, but these errors were encountered: