Add 0.71 blog post #3513
Add 0.71 blog post #3513
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
|
||
| This release includes a number of new props inspired by web standards to align React Native’s APIs across many platforms. These new props are purely additive so there are no expected migrations or change of behavior for equivalent accessibility, behavior, or style props. | ||
|
|
||
| For any new prop alias introduced, if there is an existing prop with a different name and both are specified, the new alias prop value will take precedence. For example, this release adds a `src` prop alias for `source` on the Image component to align with the `src` prop on web. If both `src` and `source` are provided, the new `src` prop will be used. |
There was a problem hiding this comment.
it is not very clear to me whether it’s recommended to use the new props or not. as in — are they going to eventually replace the old ones? coexist forever?
There was a problem hiding this comment.
It's not clear to me what the recommendation is, or if we plan to remove the old props in a future version. @necolas @lunaleaps do you know thee answer?
There was a problem hiding this comment.
Small heads up that we are going to publish the blogpost leaving this as unclear for now. It could require longer discussion and we could update the blogpost once we have more clarity on how to proceed.
|
In general, we usually do not use italic font style in docs content or in blog posts. This post includes a lot of italic stylization, with hard to detect rule, when it's applied, and when not. Can we remove it at least from the links, for the overall content consistency? |
I did a first round of review, applying the basic suggestions that have been pointed out by reviewers.
|
@Simek good call on the italics, this was applied from copying from Google Docs for some reason. |
|
|
||
| This release includes a number of new props inspired by web standards to align React Native’s APIs across many platforms. These new props are purely additive so there are no expected migrations or change of behavior for equivalent accessibility, behavior, or style props. | ||
|
|
||
| For any new prop alias introduced, if there is an existing prop with a different name and both are specified, the new alias prop value will take precedence. For example, this release adds a `src` prop alias for `source` on the Image component to align with the `src` prop on web. If both `src` and `source` are provided, the new `src` prop will be used. |
There was a problem hiding this comment.
Small heads up that we are going to publish the blogpost leaving this as unclear for now. It could require longer discussion and we could update the blogpost once we have more clarity on how to proceed.
No description provided.