Skip to content

Don't show base version in Applies_to tags if no version is defined#2630

Merged
reakaleek merged 5 commits intomainfrom
feature/fix-applies-to-parser
Feb 4, 2026
Merged

Don't show base version in Applies_to tags if no version is defined#2630
reakaleek merged 5 commits intomainfrom
feature/fix-applies-to-parser

Conversation

@reakaleek
Copy link
Member

No description provided.

@reakaleek reakaleek added the fix label Feb 4, 2026
Copy link
Member

@Mpdreamz Mpdreamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this also tackle the popovers?

@reakaleek
Copy link
Member Author

Does this also tackle the popovers?

Yes. But I already found a bug.

…on attributes

The Razor template always renders badge-lifecycle-text and badge-version attributes
(even when empty), but the test expectations for Serverless GA were missing these
required attributes, causing CI failures.
@github-actions
Copy link

github-actions bot commented Feb 4, 2026

🔍 Preview links for changed docs

@shainaraskas shainaraskas linked an issue Feb 4, 2026 that may be closed by this pull request
Razor Slices automatically removes empty string attributes from HTML output.
Updated test expectations to match actual output by removing badge-lifecycle-text
and badge-version attributes when they are empty strings, and removing badge-key
when it's not provided (generic product case).
@reakaleek reakaleek marked this pull request as ready for review February 4, 2026 17:12
@reakaleek reakaleek requested review from a team as code owners February 4, 2026 17:12
@reakaleek reakaleek requested a review from cotti February 4, 2026 17:12
Copy link
Contributor

@florent-leborgne florent-leborgne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current changes LGTM - I'm wondering about the markdown output since it's no longer showing the base version either // do we anticipate negative effects on version-related accuracy? Or do we need to think of a way to convey that the content from these pages generally applies to users on Elastic v9 unless otherwise specified // Worded in a way that can't be mistaken for "this feature is available in version xxx"

Copy link
Contributor

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same note as florent, but maybe something to deal with separately. lgtm

@reakaleek reakaleek merged commit 18d34cb into main Feb 4, 2026
31 checks passed
@reakaleek reakaleek deleted the feature/fix-applies-to-parser branch February 4, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Turn off showing the base version by default

4 participants