fix: typos and stray leading space in date format#5864
Merged
Conversation
Three small fixes from nightly survey: - anchor.rs: 'proceeding pipeline' -> 'preceding pipeline' (two doc comments); 'SELECTTed' -> 'SELECTed'. - arrays.md: 'can be vary' -> 'can vary'. - article.html: drop leading space in .Date.Format / .Lastmod.Format argument so the rendered <time datetime> attribute is a clean ISO 8601 string.
for more information, see https://pre-commit.ci
The original commit changed `SELECTTed` to `SELECTed` in the Sort requirements comment, but the typos pre-commit hook tokenizes the camelCase boundary as `SELEC` and "corrects" it back to `SELECTTed`. Use lowercase `selected` (already the convention in this file — see lines 429, 562) so the fix actually lands. Co-Authored-By: Claude <noreply@anthropic.com>
Companion to the line-565 fix in this PR. Co-Authored-By: Claude <noreply@anthropic.com>
Same fix as the article.html change in this PR — list.html had the identical leading space inside the Go time-format string passed to .Date.Format. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Findings from the nightly survey (2026-05-07). Three small documentation/correctness fixes:
prqlc/prqlc/src/sql/pq/anchor.rs: Fix two doc-comment typos referring to "proceeding pipeline" — the variable in code ispreceding, and these functions split a pipeline into the preceding (earlier) part and the atomic (last) part. Also fixSELECTTed→selectedin theSortrequirements comment (using lowercase to match the existing convention in this file —SELECTedwas reverted by the typos pre-commit hook, which tokenizes the camelCase boundary asSELECand "corrects" it back).web/book/src/reference/syntax/arrays.md: Grammar fix — "Number of fields can be vary." → "Number of fields can vary."web/website/themes/prql-theme/layouts/_default/article.html: Remove a stray leading space inside the Go time-format string passed to.Date.Format/.Lastmod.Format. The previous" 2006-01-02T15:04:05Z07:00"rendered into<time datetime=" 2026-…">with a leading space; browsers tolerate it, but the rendered attribute should be a clean ISO 8601 string.Test plan
task prqlc:testpasses