Skip to content

📝 docs(mq-lang): document =~ regex match operator; fix hash ordering and syntax highlighting#1311

Merged
harehare merged 4 commits intofeat/regex-match-operatorfrom
copilot/sub-pr-1305
Feb 21, 2026
Merged

📝 docs(mq-lang): document =~ regex match operator; fix hash ordering and syntax highlighting#1311
harehare merged 4 commits intofeat/regex-match-operatorfrom
copilot/sub-pr-1305

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 21, 2026

  • Add documentation for the =~ regex match operator to docs/books/src/reference/comparisons.md
  • Fix HASH_IS_REGEX_MATCH alphabetical ordering in builtin.rs
  • Fix =~ placement in assets/mq.sublime-syntax
  • Fix if example syntax to use if (expr): expr else: expr form

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…sh constant ordering and sublime-syntax operator placement

Co-authored-by: harehare <[email protected]>
Copilot AI changed the title [WIP] Add =~ regex match operator and is_regex_match builtin 📝 docs(mq-lang): document =~ regex match operator; fix hash ordering and syntax highlighting Feb 21, 2026
Copilot AI requested a review from harehare February 21, 2026 06:09
@harehare
Copy link
Copy Markdown
Owner

@copilot
Since the 'if' syntax is if (expr): expr else: expr, please fix the document.

Copy link
Copy Markdown
Contributor Author

Copilot AI commented Feb 21, 2026

@copilot
Since the 'if' syntax is if (expr): expr else: expr, please fix the document.

Fixed in commit 1ad1278. The example now uses the correct if (expr): expr else: expr syntax:

"foo bar" | if (. =~ "foo"): "matched" else: "no match"
# => matched

@harehare harehare marked this pull request as ready for review February 21, 2026 06:28
@harehare harehare merged commit 168dedb into feat/regex-match-operator Feb 21, 2026
@harehare harehare deleted the copilot/sub-pr-1305 branch February 21, 2026 06:39
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