Conversation
📝 WalkthroughWalkthroughThe README.md file was updated to specify a new major version requirement for the Modern Timeline extension in installation instructions, changing the Composer package version from "~1.0" to "~2.0". A minor correction was also made in the contribution section, updating the link text from "Professional.Wiki" to "Professional Wiki". Changes
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
README.md (2)
42-45: Use spaces instead of hard tabs & switch to caret version constraintThe JSON snippet keeps hard-tab indentation on lines 42-44 (MD010) and pins the package with
~2.0, which only allows2.0.*.
Consider switching to spaces and a caret to get all minor/patch releases of v2.- "require": { - "professional-wiki/modern-timeline": "~2.0" + "require": { + "professional-wiki/modern-timeline": "^2.0"
48-53: Fence the single-line snippet to satisfy MD046The indented line renders as a code block but violates markdownlint’s “fenced” style rule. Wrap it in back-ticks (and, optionally, adopt the caret constraint for consistency).
- "professional-wiki/modern-timeline": "~2.0" +```json +"professional-wiki/modern-timeline": "^2.0" +```
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md
43-43: Hard tabs
Column: 1
(MD010, no-hard-tabs)
44-44: Hard tabs
Column: 1
(MD010, no-hard-tabs)
51-51: Code block style
Expected: fenced; Actual: indented
(MD046, code-block-style)
|
|
||
| [Professional MediaWiki support](https://professional.wiki/en/support) is available via | ||
| [Professional.Wiki](https://professional.wiki/). | ||
| [Professional Wiki](https://professional.wiki/). | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Ensure all occurrences of the old “Professional.Wiki” label are updated
This fix touches one instance, but there may be more. Quick verification:
🏁 Script executed:
rg --ignore-case "Professional\.Wiki" README.md docsLength of output: 784
🏁 Script executed:
#!/bin/bash
# Search specifically for link labels using the old "Professional.Wiki" text
rg -n "\\[Professional\\.Wiki\\]" --ignore-case --glob "*.md"Length of output: 134
Update remaining “Professional.Wiki” link label
Search uncovered one more occurrence in README.md that needs updating:
- README.md:151
- Contact [Professional.Wiki](https://professional.wiki/) for + Contact [Professional Wiki](https://professional.wiki/) for
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In README.md around lines 151, update the link label from “Professional.Wiki” to
“Professional Wiki” to maintain consistent branding. Locate the link text and
modify it accordingly without changing the URL.
2 participants
Summary by CodeRabbit