-
Notifications
You must be signed in to change notification settings - Fork 38
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
Convention for metadata written by tasks #20
Comments
Can you describe with more details why that might be useful? |
I was just thinking that if perun encourages people to extend it with other tasks there probably should be some convention about how/where they store task related data. Given we change the {:io.perun {:markdown/html "<h1>Title</h1>"
:ttr "2min"}} i.e. there is some loose mapping from task name to the keys the tasks write to. Currently the markdown task writes to |
Not 100% sure about this. In such case tasks further in the chain need to know name of props like |
I see your general point but doesn't the renderer function now equally need to be aware of
Making them customizable is probably a good idea in any case. |
I'm thinking that if you replace Another idea: we can have some global option that turns namespacing on/off. This way we might have both solutions. |
@podviaznikov I'll think about this a bit more but one thing to keep in mind is that the |
@Deraen do you have thoughts on establishing some sort of convention for tasks and the keys in metadata they're writing to? |
Not really. But I would avoid anything which prevents using |
The real problem with this is that it would mean that you could never use the same renderer for something in markdown and something in some other format. Overall, format is an implementation detail, and a website could have both markdown files and HTML fragments. Both of these may want to use the same templating. |
Hi, @Deraen @martinklepsch @podviaznikov @MartyGentillon , There hasn't been any activity on this thread for over three years... |
Probably a good idea to establish some sort of namespacing for metadata i.e.
perun/markdown
can only write to:perun/markdown
key in metadata.The text was updated successfully, but these errors were encountered: