Update outdated docs, improve naming, prefer user props over auth hook in docs #2535
Conversation
| @@ -8,6 +8,7 @@ | |||
| /docs/deploying /docs/deployment/intro 301 | |||
| /docs/advanced/deployment/overview /docs/deployment/intro 301 | |||
| /docs/integrations/css-frameworks /docs/project/css-frameworks 301 | |||
| /docs/data-model/backends /docs/data-model/databases 301 | |||
There was a problem hiding this comment.
Hm but this is probably not 1 on 1 mapping? I am guessing that backends was wider than just databases? If it is just name change then makews sense, but if not and backends was wider, maybe better not to map at all?
There was a problem hiding this comment.
It's fine - the backends refered to "database backends". The new "databases" site is exactly that with a couple of extra sentences and an extra title added on top.
| @@ -8,6 +8,7 @@ | |||
| /docs/deploying /docs/deployment/intro 301 | |||
| /docs/advanced/deployment/overview /docs/deployment/intro 301 | |||
| /docs/integrations/css-frameworks /docs/project/css-frameworks 301 | |||
| /docs/data-model/backends /docs/data-model/databases 301 | |||
There was a problem hiding this comment.
It's fine - the backends refered to "database backends". The new "databases" site is exactly that with a couple of extra sentences and an extra title added on top.
|
@FranjoMindek did I get something wrong, or did you add quite some changes after my last review -> what happened there? Are those still in the initial scope of this PR, or are these additional fixes? |
|
Initial commit didn't capture all places referencing the old name of the document. I've added rest of them. |
awaitforsanitizeAndSerializeProviderDatacallsdata-model/backendstodata-model/databasesuserprops rather thanuseAuth(), also reflected on examplesRelated issues: #2514, #1071