Fix useSubmission/useSubmissions and action docs #1179
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
✅ Deploy Preview for solid-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 tasks
42fee24 to
fbdec7a
Compare
fbdec7a to
73da3ce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description(required)
Related issues & labels
useSubmission&useSubmissions#1026, [Content]: ClarifyuseSubmission(s)Documentation to Emphasize Actions Over Form Submissions #1024, [Content]: Remove the useSubmission/useSubmissions section in theactionreference #1003, [Content]: Confusing language for useAction #1192, Proper Usage of action and with Method in Solid Router #791, Server Action: Link to benefits from API Reference #981, [Content]: the preload explanation about cache is very vague How much time does it cache the route or is this only caching the route data not the route itself as after render #1173