Expose the renderer classes for use outside of the context of the MarkdownPostProcessor #361
Replies: 2 comments
-
This looks amazing. I want this 🤩 I don’t quite understand what you need me to do. Could you please elaborate a bit? How could I make the query renderer variable available to another plugin? I haven’t done interaction between plugins. Regarding Let me know how I can support! Thank you for digging in and checking it this far! I plan to get back into the code base the coming week. But I have been absent for quite a while, so I will need some time 😅 |
Beta Was this translation helpful? Give feedback.
-
Thanks for the interest in this idea. I've created a PR here #363 with an example of how I enabled this and a bit of sample code showing how I'm leveraging it externally. I'm sure there are multiple ways to go about exposing the methods though so feel free to accept the PR or close it and implement it however you see fit. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If you could assign variables to your renderer classes, it would allow my CodeMirror Options plugin to render task code blocks in edit mode. If you have other suggestions for how to access these classes, I'm open to alternative approaches:
https://github.com/schemar/obsidian-tasks/blob/7f9f80cedbf10aeb916d4041d2adda558bc1e02a/src/main.ts#L33
It looks like I would also need a
this
bound version ofaddQueryRenderChild
https://github.com/schemar/obsidian-tasks/blob/7f9f80cedbf10aeb916d4041d2adda558bc1e02a/src/QueryRenderer.ts#L31
This would allow for this type of functionality:

Beta Was this translation helpful? Give feedback.
All reactions