Asciidoc-vscode recently dropped functionality to use external processor (any of those mentioned), so now there is no official mean to use other extensions. AsciidocFX can be hacked to include js-based plugins, according to its maintainers. * Perhaps the AsciiDoc WG can play an arbitration role. AsciidocFX, asciidoc-vscode, Adobe Brackets and Atom make use of asciidocjs engine. I think, in many ways, they are leading the way on what it means to support AsciiDoc properly in a repository browser, and hopefully others will follow. Where you do see these display features implemented is on GitLab. And they simply refuse to implement certain display features, despite countless pleas from the community. An option is, that AsciidoctorFX (or the installed/used Asciidoctor version) does not replace the place holders (parent-class, child-class) correctly and just give plantuml the plain, unchanged plantuml code - looking at the error message this looks very likely to be the problem. But at the end of the day, it's their platform and their choice. And there's literally nothing we can do about it*. It just means GitHub is not providing a full fidelity experience. Installing an Asciidoctor processor is just the beginning of your publishing experience. Path: "$ = V D) But just because GitHub won't render something doesn't make it not AsciiDoc. Uses: name: "Generate site using antora site action" To know more just drop by the asciidoctor gitter channels or the forum. The only thing to adapt is the "Generate site using antora site action", the rest is always the same. The tricky part is using upload-artifact and download-artifact to share the resulted converted docs in HTML between conversion and push steps. Here is an example of a GH-Action that publishes and Antora/Asciidoctor site on GH-Pages when a change on "main" branch is done, docs are in a folder called "docs" alongside the code. Sorry, something went you much! Without understanding it better or having some clear examples of how it might work in my specific context, the idea of allowing an action to commit changes makes me nervous. It's true that GitLab team has been more open to imprevements that GitHub, work with the later is slower. Said that, on the bright side, intellij plugin offers the best experience so far in local, with a decent preview, autocomplete and refactor features.ĭoes this work in GitLab? github/markup#1095 isn't stagnant, but I didn't see anything that looked especially promising at a glance. Overall, I'd recomend not to try to get a 100% accurate local preview or repository UI preview, complex doc builds just will require doing a full conversion. Just guessing, but if you are using something like include::my-part.adoc I doubt the plugin is able get the path. I've also tried using the AsciiDoc chrome plugin in Brave with no luck properly rendering adocs with include directives in them on GitHub either. But with GH-Actions the procres is made really easy. Not in GitHub, but they do work in Gitlab. This supported somehow without making use of a process-and-commit pipeline, whether by workaround or not?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |