You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just looking at an issue related to mdxSource and did a search for it in our codebase to verify that it had been removed in v8. It has been completely removed, but there is still a single reference in the docs:
Provides source to display. Use [`source.code`](#source) instead.
Looking around in that file, it looks like there are other v8 removals that are also still present in the docs. Somebody should do an audit and make sure that everything that we removed from code in v8 has also been removed from the docs.
Additional context
No response
The text was updated successfully, but these errors were encountered:
For context, the APIs for the Doc Blocks were already addressed, mostly during the work towards the beta by the team. The one referenced here was already removed with #25855. However, there's still a lingering reference to the storiesOf that is currently being addressed in a pull request that I've pushed, and I'm waiting on feedback. If there were any APIs for addons, that should have been addressed with the beta release, to which I asked for for a sanity check and to the best of my knowledge they were removed. If there's any lingering ones, they should have been thoroughly vetted previously.
Describe the problem
I was just looking at an issue related to
mdxSource
and did a search for it in our codebase to verify that it had been removed in v8. It has been completely removed, but there is still a single reference in the docs:storybook/docs/api/doc-block-canvas.md
Lines 231 to 237 in 69fcf16
Looking around in that file, it looks like there are other v8 removals that are also still present in the docs. Somebody should do an audit and make sure that everything that we removed from code in v8 has also been removed from the docs.
Additional context
No response
The text was updated successfully, but these errors were encountered: