-
Notifications
You must be signed in to change notification settings - Fork 967
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
Add path annotation for codeblock #2610
base: next
Are you sure you want to change the base?
Conversation
What's the main usage for it? Is it be displayed or retrieve by the frontend? |
For now I use it like so:
I find useful to have the required file path associated with the code block when blogging about specific tool configuration. Some tools expect configuration at pre determined paths |
I agree it's nice, I'm just wondering if it doubles as the code sample name as well potentially? |
Ah can you rebase the PR? It looks like it's got some unrelated stuff due to the last release |
Yes I agree it could be the name. I can change |
1d85d80
to
d73d4a2
Compare
I rebased the branch |
Let's call it name, this way it can be used for more stuff. |
Should be good :) |
https://zola.discourse.group/t/allow-to-specify-path-associated-with-a-codeblock/2253
Sanity check:
Code changes
(Delete or ignore this section for documentation changes)
next
branch?If the change is a new feature or adding to/changing an existing one: