Skip to content
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

Possible improvements to YAML frontmatter handling? #12703

Closed
TrollDecker opened this issue Sep 3, 2020 · 4 comments
Closed

Possible improvements to YAML frontmatter handling? #12703

TrollDecker opened this issue Sep 3, 2020 · 4 comments
Labels
issue/stale type/upstream This is an issue in one of Gitea's dependencies and should be reported there

Comments

@TrollDecker
Copy link

  • Gitea version (or commit ref): 1.12.3

Description

👋 🙂

Thank you for the frontmatter formatting thingy for Markdown files. Really helps to tidy things up.
Only thing is, I think there's a bit of room for improvement?

For a start, I'm not keen on having each field be a column, because it squishes everything up when it reaches page width and just makes things messy, like in the screenshot below. Would it not make more sense to have each field be a row instead? If need be, possibly collapsible ones?

And in addition, I feel like YAML collections should be treated more like lists? in the below screenshot, they just render as something akin to an array without any comma separation, making it near impossible to tell single- and multi-word items apart. Less than ideal.

Screenshots

Screenshot_2020-09-03 BookData(1)

@zeripath
Copy link
Contributor

zeripath commented Sep 3, 2020

The rendering essentially comes from yuin/goldmark-meta so it might be better to put a feature request there.

However there are a couple of options which gitea provides: setting the gitea value or the gitea meta value to none will hide it, table will show the table and details will hide the table behind a details and summary.

@lunny lunny added the type/upstream This is an issue in one of Gitea's dependencies and should be reported there label Sep 3, 2020
@TrollDecker
Copy link
Author

Ah, fair enough, thanks. 😅

@stale
Copy link

stale bot commented Nov 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@6543
Copy link
Member

6543 commented Apr 30, 2022

not possible for now see yuin/goldmark-meta#6

@6543 6543 closed this as completed Apr 30, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/upstream This is an issue in one of Gitea's dependencies and should be reported there
Projects
None yet
Development

No branches or pull requests

4 participants