Add asciidoc support for generated plugin list#72292
Add asciidoc support for generated plugin list#72292stacey-gammon merged 16 commits intoelastic:masterfrom
Conversation
0edf151 to
ae995aa
Compare
45466c9 to
a8d024d
Compare
|
@elasticmachine run elasticsearch-ci/docs |
a8d024d to
a1131b2
Compare
|
@elasticmachine run elasticsearch-ci/docs With any luck this will finally pass! |
1d4a2d0 to
9beaa8a
Compare
|
@spalger - any idea why this would fail with "js file outside regularBundlesPath"? |
|
That looks a lot like an Angular provider converted to JSON... |
9beaa8a to
4bb7f5a
Compare
|
I'll sync with master again and 🤞 |
|
Looks like it's opal-runtime, which is installed by asciidoctor and provides a runtime to run ruby code that's transformed to JS... This seems like an unnecessary amount of impact for a text parser, and the fact that it's injecting globals and breaking tests is pretty concerning. Is there another dependency we can use besides asciidoctor? If not, maybe we can consume it through the CLI rather than via the node API? |
2d6c609 to
b83d12a
Compare
|
@elasticmachine run elasticsearch-ci/docs |
|
@stacey-gammon looks like all tests are passing 🙌 ! |
|
@elasticmachine run elasticsearch-ci/docs Thanks @gtback! I lost track of this PR for a couple days. :) |
Try level offset "=+2" instead of "=+1" to stop the inlining of the includes. remove +2 back to +1
b83d12a to
acc37d9
Compare
…ciidoc-support-for-plugin-list
… the paragraph snippet.
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
@stacey-gammon when we make changes to the readme files, and then in turn update the plugin list in the docs, are we verifying the syntax is valid in CI? (via elasticsearch-ci/docs I assume) |
|
@spalger yes, any of the Asciidoc files that get included in the build process will be validated by |
spalger
left a comment
There was a problem hiding this comment.
LGTM, one little totally ignorable nitpick
| const { firstParagraph, anchor } = extractAsciidocInfo( | ||
| `[[this-is-the-anchor]] | ||
| == Heading here | ||
|
|
||
| Intro. | ||
|
|
||
| === Another heading | ||
|
|
||
| More details` | ||
| ); | ||
|
|
||
| expect(firstParagraph).toEqual(`Intro.`); | ||
| expect(anchor).toEqual('this-is-the-anchor'); |
There was a problem hiding this comment.
I'm sure you've got your reasons for not preferring this, but wanted to suggest considering inline snapshots
import dedent from 'dedent';
//...
expect(
extractAsciidocInfo(dedent`
[[this-is-the-anchor]]
== Heading here
Intro.
=== Another heading
More details
`)
).toMatchInlineSnapshot(...autogenerated by jest...)|
Thought I merged this weeks ago 🤦♀️ . |
| [[dashboard-enhanced-plugin]] | ||
| == Dashboard app enhancements plugin | ||
|
|
||
| Adds drilldown capabailities to dashboard. Owned by the Kibana App team. |
There was a problem hiding this comment.
Seems to be a typo here (capabailities):
| Adds drilldown capabailities to dashboard. Owned by the Kibana App team. | |
| Adds drilldown capabilities to dashboard. Owned by the Kibana App team. |
There was a problem hiding this comment.
Fixed, thanks for the review!
kertal
left a comment
There was a problem hiding this comment.
Apart from a minor typo, KibanaApp owned code LGTM. didn't test.
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
* add asciidoc support for generated plugin list Try level offset "=+2" instead of "=+1" to stop the inlining of the includes. remove +2 back to +1 * Remove asciidoc, switch to regex. Rearrange dev guide to avoid nesting limit. * Add tests for regex * add a description to not throw off the table. Remove the heading from the paragraph snippet. * Fix more READMEs so table renders correctly * Update plugin list * Remove code-exploration file, moved to plugin-list * fix typo * Add link to developer examples * Update plugin list * fix typo # Conflicts: # docs/developer/architecture/code-exploration.asciidoc
* add asciidoc support for generated plugin list Try level offset "=+2" instead of "=+1" to stop the inlining of the includes. remove +2 back to +1 * Remove asciidoc, switch to regex. Rearrange dev guide to avoid nesting limit. * Add tests for regex * add a description to not throw off the table. Remove the heading from the paragraph snippet. * Fix more READMEs so table renders correctly * Update plugin list * Remove code-exploration file, moved to plugin-list * fix typo * Add link to developer examples * Update plugin list * fix typo # Conflicts: # docs/developer/architecture/code-exploration.asciidoc
* add asciidoc support for generated plugin list Try level offset "=+2" instead of "=+1" to stop the inlining of the includes. remove +2 back to +1 * Remove asciidoc, switch to regex. Rearrange dev guide to avoid nesting limit. * Add tests for regex * add a description to not throw off the table. Remove the heading from the paragraph snippet. * Fix more READMEs so table renders correctly * Update plugin list * Remove code-exploration file, moved to plugin-list * fix typo * Add link to developer examples * Update plugin list * fix typo # Conflicts: # docs/developer/architecture/code-exploration.asciidoc
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
Adds README asciidoc support so READMEs in asciidoc are now part of the developer guide:
Also:
Developer Guide -> Architecture -> Code exploration -> Plugin Readmesit's nowDeveloper Guide -> Plugin list -> Plugin READMEs. I think it's more discoverable there anyway.Change the name and contents of the file. The text about the folder hierarchy best practices didn't seem to go in there and just made a long page longer. Now it's just a table of plugins.
Made it a table for better readability:
Before:

After:
