Add a tip pointing to code splitting #4236
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
name: 📖 Add a tip pointing to code splitting
about: Updating content in an existing docs page
PR Type
update an existing page
Checklist
What docs page is being added or updated?
For Updating Existing Content
What updates should be made to the page?
The main goal is to highlight the fact that you're expect to have only one
createApi
call in the app. (Maybe it's rather one per API, as in, if it's a different server, it's a differentcreateApi
?). I'm also putting a link to the advanced concept ofInjecting endpoints
that people most likely want when callingcreateApi
multiple times.Do these updates change any of the assumptions or target audience? If so, how do they change?
I don't think so.