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.
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
docs: Grammar overhaul #20636
docs: Grammar overhaul #20636
Conversation
Β Open in CodeSandbox Web Editor | VS Code | VS Code Insiders |
β Live Preview ready!
|
Done with the sixth batch! Noticed the config documentation is a bit lacking so I will work on it in the meantime, but definitely send the 7th batch whenever you can! |
@danielroe Could I please get a confirmation that my latest commit will, in fact, show autoImport? |
packages/schema/src/config/adhoc.ts
Outdated
/** | ||
* Toggle auto-imports for all composables, components, directories, and all other parts of your application that Nuxt usually handles. | ||
*/ | ||
autoImport: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, good catch - this will mean it shows up in the nuxt.config
generated markdown... You ca n preview the result by running pnpm build:stub
(or pnpm build
) and checking packages/schema/schema/config.md
which will be generated.
It would be good to sync the docs between here and ../src/types/imports
so the text and examples are the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, thanks for confirming! Turns out preview was indeed the issue in displaying as it did not generate the page when going there, because at first I thought I broke it haha. Always glad to help! Will sync it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seventh batch of comments
@@ -149,10 +149,10 @@ export default defineEventHandler(async (event) => { | |||
You can now universally call this API using `$fetch('/api/submit', { method: 'post', body: { test: 123 } })`. | |||
|
|||
::alert{type=warning title=Attention} | |||
We are using `submit.post.ts` in the filename only to match requests with `POST` method that can accept the request body. When using `readBody` within a GET request, `readBody` will throw a `405 Method Not Allowed` HTTP error. | |||
We use `submit.post.ts` in the filename only to match requests with the `POST` method that can accept the request body. When using `readBody` within a GET request, `readBody` will throw a `405 Method Not Allowed` HTTP error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use `submit.post.ts` in the filename only to match requests with the `POST` method that can accept the request body. When using `readBody` within a GET request, `readBody` will throw a `405 Method Not Allowed` HTTP error. | |
We use `submit.post.ts` filename to match requests only with the `POST` method (that can accept the request body). When using `readBody` within a GET request, `readBody` will throw the HTTP `405 Method Not Allowed` response status code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about adding a the
before submit.post.ts
?
@@ -21,12 +21,12 @@ function useMyComposable () { | |||
Plugins also receive `nuxtApp` as the first argument for convenience. [Read more about plugins.](/docs/guide/directory-structure/plugins) | |||
|
|||
::alert{icon=π} | |||
**`useNuxtApp` (on the server) only works during `setup`, inside Nuxt plugins or `Lifecycle Hooks`**. | |||
**`useNuxtApp` (on the server) only works during `setup` inside Nuxt plugins or `Lifecycle Hooks`**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing comma changed the meaning of the sentence :)
Also, worth having a look: https://www.proofreadnow.com/blog/putting-only-in-its-place
**`useNuxtApp` (on the server) only works during `setup` inside Nuxt plugins or `Lifecycle Hooks`**. | |
**`useNuxtApp` (on the server) works only during component's `setup` function, lifecycle hooks and inside Nuxt plugins.** |
Co-authored-by: Damian GΕowala <48835293+DamianGlowala@users.noreply.github.com>
This is such a big PR, and therefore could easily get out of sync with main branch. What do you think about splitting it up into smaller concept-based chunks which can be more easily reviewed and merged in incrementally? |
It certainly is, and I am only halfway through the reviewing process. It will be equally time-consuming for anyone to review once we're done with amendments. I like this idea. Let's wait for what Michael says. We could continue making amendments here until I'm done, and then start splitting this finalised big PR into smaller chunks which can be more easily reviewed. |
If you guys think it would be the smarter idea, I'm down. It's just that I read that docs updates should be grouped and sent as a batch which is what I did. The bigger question here would be how to split this now that it has gotten this big. |
Co-authored-by: Damian GΕowala <48835293+DamianGlowala@users.noreply.github.com>
Co-authored-by: Damian GΕowala <48835293+DamianGlowala@users.noreply.github.com>
Maybe you could split by folder?
(each item could be a PR) which will make a good number of pr! |
Hmm, it might be good, but that would mean I'll have to open multiple PR's, wouldn't it? I dont want to be a bother and spam too much. And would I be able to open a PR and just drag and drop the files I have in this branch to each PR accordingly? |
I think it's not spam because PR are meaning full. And yes, you can easily create a PR with drag and drop. (https://docs.github.com/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository) |
See my comment in #21040 (comment). I hate to close this as it has so many good changes, but it will be too tricky to merge + review. π’ |
Grammatical improvement for the page, with better consistency and punctuation usage.
π Linked issue
Also implements #20706 for a unified merge with the overhaul
β Type of change
π Description
This PR fixes the grammar throughout the documentation, giving a more professional look to nuxt. (As of latest commits, this has become a general-purpose docs PR)
π Checklist