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
Not a frequent occurrence, but it does happen, e.g. the <MapMarker> component in https://v3.svelte.technology/tutorial/context-api
<MapMarker>
The text was updated successfully, but these errors were encountered:
I've looked into this a bit, and I wonder if it isn't nicer just to keep a DOM-less component fragment looking like this...
function create_fragment(ctx) { return { c: noop, l: noop, m: noop, p: noop, i: noop, o: noop, d: noop }; }
...rather than checking for the existence of $$.fragment throughout the runtime code, since it's such a special case.
$$.fragment
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Not a frequent occurrence, but it does happen, e.g. the
<MapMarker>
component in https://v3.svelte.technology/tutorial/context-apiThe text was updated successfully, but these errors were encountered: