You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to have top aligned Name column in the table for our generated macro documents.
The reason for this is because sometimes we have quite much text in the Description column and then the Name is hard to see when it's aligned in the middle.
We have tried to keep the Markdown format in the template and achieve this but have failed with that.
Instead of:
Sorry for the delay in a response to this and other issues you've filed. At the moment we have plans to rework how Stardoc integrates with Bazel so that it's less brittle. This unfortunately means that we're not prioritizing feature requests and formatting issues unless they majorly impact Stardoc's usability or are clear regressions.
Thanks @brandjon for your response,
This is not the most prioritized task with our own documentation.
As I said previous, we can live with our html-template.
I think that it will be great if Stardoc gets improved and uses a Bazel evaluation then I think/hope that using Stardoc rules will work the same as using Bazel. In another ticket I have filed about dependencies for example shows how it differs. So I look forward to the updated Stardoc :-)
Hi,
We want to have top aligned Name column in the table for our generated macro documents.
The reason for this is because sometimes we have quite much text in the Description column and then the Name is hard to see when it's aligned in the middle.
We have tried to keep the Markdown format in the template and achieve this but have failed with that.
Instead of:
We have now added html to be able to get the alignment:
It's not what we prefer since it will not be as nice to read as Markdown.
Do you have any idea how to fix this and still keep the Markdown format?
We can live with our html in the template but it's not the preferred solution.
Thanks!
The text was updated successfully, but these errors were encountered: