Skip to content

Change comments in line protocol syntax to be self-descriptive # - #7678

Closed
maximal wants to merge 1 commit into
influxdata:masterfrom
maximal:patch-2
Closed

Change comments in line protocol syntax to be self-descriptive ##7678
maximal wants to merge 1 commit into
influxdata:masterfrom
maximal:patch-2

Conversation

@maximal

@maximal maximal commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Similar to #5821.

@maximal
maximal requested a review from a team as a code owner August 20, 2026 12:35
@maximal
maximal requested review from jstirnaman and removed request for a team August 20, 2026 12:35
jstirnaman added a commit that referenced this pull request Aug 25, 2026
#7678 and #5821 fixed the misleading `js`/`//` comment syntax in the
line protocol "Syntax" block, but relabeled it `python`, which is
still not what the block is (a placeholder grammar, not runnable
Python or JS). Split each occurrence into a `text` fence for the
placeholder syntax and a standalone `lp` fence for the real example,
matching this repo's line-protocol fence convention. Also fixed the
several other `js`/`sh`-tagged blocks in the same two shared files
that are real, standalone line protocol (not templates) to use `lp`,
since they were failing codeblock lint as invalid JavaScript.

PR #5821 targeted content/influxdb/v2/reference/syntax/line-protocol.md,
which is now a stub whose body is sourced from
content/shared/influxdb-v2/reference/syntax/line-protocol.md; applied
its intent to the shared file instead.

Co-authored-by: MaximAL <almaximal@gmail.com>
@jstirnaman

Copy link
Copy Markdown
Contributor

Thanks for the fix! Folded into #7705, which also splits the syntax template from the runnable example (so it's not mislabeled as python either) and applies the same fix to the other line-protocol reference pages. Your commit is preserved in that branch's history and credited via co-author trailer. Closing this in favor of #7705.

@jstirnaman jstirnaman closed this Aug 25, 2026
@maximal

maximal commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

@jstirnaman, thanks!

jstirnaman added a commit that referenced this pull request Aug 25, 2026
#7678 and #5821 fixed the misleading `js`/`//` comment syntax in the
line protocol "Syntax" block, but relabeled it `python`, which is
still not what the block is (a placeholder grammar, not runnable
Python or JS). Split each occurrence into a `text` fence for the
placeholder syntax and a standalone `lp` fence for the real example,
matching this repo's line-protocol fence convention. Also fixed the
several other `js`/`sh`-tagged blocks in the same two shared files
that are real, standalone line protocol (not templates) to use `lp`,
since they were failing codeblock lint as invalid JavaScript.

PR #5821 targeted content/influxdb/v2/reference/syntax/line-protocol.md,
which is now a stub whose body is sourced from
content/shared/influxdb-v2/reference/syntax/line-protocol.md; applied
its intent to the shared file instead.

Co-authored-by: MaximAL <almaximal@gmail.com>
jstirnaman added a commit that referenced this pull request Aug 25, 2026
#7678 and #5821 fixed the misleading `js`/`//` comment syntax in the
line protocol "Syntax" block, but relabeled it `python`, which is
still not what the block is (a placeholder grammar, not runnable
Python or JS). Split each occurrence into a `text` fence for the
placeholder syntax and a standalone `lp` fence for the real example,
matching this repo's line-protocol fence convention. Also fixed the
several other `js`/`sh`-tagged blocks in the same two shared files
that are real, standalone line protocol (not templates) to use `lp`,
since they were failing codeblock lint as invalid JavaScript.

PR #5821 targeted content/influxdb/v2/reference/syntax/line-protocol.md,
which is now a stub whose body is sourced from
content/shared/influxdb-v2/reference/syntax/line-protocol.md; applied
its intent to the shared file instead.

Co-authored-by: MaximAL <almaximal@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants