-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Fix hard coded URL domain #15329
[docs] Fix hard coded URL domain #15329
Conversation
- The `columnVisibilityChange` event was removed. Use [`columnVisibilityModelChange`](https://mui.com/x/react-data-grid/events/#catalog-of-events) instead. | ||
- The `columnVisibilityChange` event was removed. Use [`columnVisibilityModelChange`](https://v6.mui.com/x/react-data-grid/events/#catalog-of-events) instead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Migration guide, we likely don't want to have to care about keeping those links working, they might not even stay relevant with different majors.
Deploy preview: https://deploy-preview-15329--material-ui-x.netlify.app/ Updated pages: |
If the filter operator has a [custom `InputComponent`](https://mui.com/x/react-data-grid/filtering/#custom-input-component), the same component is being used for the header filter. | ||
If the filter operator has a [custom `InputComponent`](/x/react-data-grid/filtering/customization/#custom-input-component), the same component is being used for the header filter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That link was broken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't caught by the link-check
because of the full URL I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct
A side quick win I noticed while wanting to help with #15251.
The objective of this change is to:
It's relevant for docs versioning too. We use subdomains today, so it would point to the wrong domain. If we moved to do docs versioning with subfolders, it would also have the wrong URL prefix.
@vladmoroz We likely don't want to start thinking now on how we will version Base UI, etc. docs. I have seen it's common to use subfolders (Material UI used subdomains so far), maybe they do this for SEO to reinforce backlinks on a single domain, or maybe to make it impossible to have duplication of other pages, e.g. marketing homepage.
Anyway, creating this page as we have time: https://www.notion.so/mui-org/docs-infra-How-to-version-docs-138cbfe7b66080f78d3bd679deec8fa9.