Skip to content
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.

Sign up for GitHub

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

[blog] Add link to Base UI API changes RFC #41089

Merged
merged 3 commits into from
Feb 15, 2024
Merged

[blog] Add link to Base UI API changes RFC #41089

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ad97fa5
[blog] Add link to Base UI API changes RFC
michaldudak Feb 14, 2024
9039320
Update docs/pages/blog/base-ui-2024-plans.md
michaldudak Feb 14, 2024
d033908
Update
michaldudak Feb 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/pages/blog/base-ui-2024-plans.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,11 @@ Additionally, since the `slots` and the corresponding `slotProps` are not relate
To address these issues, we're considering adopting a new API that would assign a discrete subcomponent to each DOM node—the pattern favored by many other headless component libraries (think: `<Slider.Track />`, `<Slider.Thumb />`, etc.).
This pattern has the potential to radically improve the customization experience, both for styles and structure.

We're still fleshing out the details and plan to release an RFC on GitHub in the coming days.
We'll update this blog post with the link when it's available.
We're still fleshing out the details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We're still fleshing out the details.
We're still fleshing out the details, but we know

(then the line below continues). @samuelsycamore, how about this so it's more connected to the next sentence? It reads a bit more natural to me that way!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, these sentences could be in different paragraphs. The fact that we're working on the API details is a separate piece of information that that we want a smooth migration path.

What do you think about:

We are still fleshing out the API and implementation details. If you have any questions or remarks about this change, chime in on the RFC on GitHub.

We know that a significant number of projects depend on the existing API, and we want to assure you that one of our top priorities is to provide a smooth migration experience.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds great to me! 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect!

We know that a significant number of projects depend on the existing API, and we want to assure you that one of our top priorities is to provide a smooth migration experience.

If you have any questions or remarks about this change, feel free to comment on the [RFC](https://github.com/mui/material-ui/discussions/41085) we recently published.

## More thorough animation support

Animation is a key element for adding delight to any application.
Expand Down
Loading