-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
fix livecodes template #2392
fix livecodes template #2392
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit c69f598:
|
.livecodes/react.json
Outdated
"jotai/vanilla/utils": "{{LC::TO_DATA_URL(./dist/esm/vanilla/utils.mjs)}}", | ||
"jotai/react/utils": "{{LC::TO_DATA_URL(./dist/esm/react/utils.mjs)}}" | ||
"customSettings": { | ||
"jotai commit number used": "can we show something here?", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hatemhosny It doesn't have to be in customSettings
, but is there a way to show the commit used in the imports?
Size Change: 0 B Total Size: 70.8 kB ℹ️ View Unchanged
|
Preview in LiveCodesLatest commit: c69f598
See documentations for usage instructions. |
Please note that the editors (markup, style, script) can have a You may use this to log commit number without showing that code in the editor. https://livecodes.io/docs/configuration/configuration-object#markup |
Yeah, but I'm thinking about removing "imports" in custom settings, say, to reproduce a bug. So, it makes sense to have the sha close to "imports". |
for convenience, you can now also use I have also updated the docs to highlight the fact that Thank you |
sorry, fixed short sha! |
#2386 (comment)