-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sync with main repo @ 9a282371 #36
Open
blitzjs-bot
wants to merge
98
commits into
main
Choose a base branch
from
sync-9a282371
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: Andreas Bollig <andreas.bollig@gmail.com> Co-authored-by: Abu Uzayr <abu.uzayr@builtforfifty.com> Co-authored-by: François Best <francois@francoisbest.com> Co-authored-by: Faraz Patankar <farazpatankar@gmail.com> Co-authored-by: Eric Vicenti <ericvicenti@users.noreply.github.com> Co-authored-by: Alex <alex@dolo.dev>
Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Andreas Bollig <andreas.bollig@gmail.com> Co-authored-by: Abu Uzayr <abu.uzayr@builtforfifty.com> Co-authored-by: François Best <francois@francoisbest.com> Co-authored-by: Faraz Patankar <farazpatankar@gmail.com> Co-authored-by: Eric Vicenti <ericvicenti@users.noreply.github.com> Co-authored-by: Layne Geck <layne.geck@gmail.com> Co-authored-by: gstranger <36181416+gstranger@users.noreply.github.com> Co-authored-by: Andrea Rizzello <10348930+andrearizzello@users.noreply.github.com>
Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Jahred Hope <jahredhope@gmail.com> Co-authored-by: Fran Zekan <zekan.fran369@gmail.com>
* new maintainer TommasoBruno added * href TommasoBruno maintainer changed
Added to `cli-start.mdx` & `cli-dev.mdx`
* typo fix Small typo fix: you'll need to do the chech => you'll need to do the check * Update session.create > session.$create * Update api routes doc examples - no anon exports * Edit preview mode doc examples - no anon exports * Change export name to handler * Change export name to handler
Typo removed
Co-authored-by: Roshan Manuel <Roshan,manuel@angelic-group.com>
If you try to copy-paste the examples there's a missing import
When you impersonate another use it would be a good idea to assumer their role too. Most endpoints will be protected with some for of authorizer e.g. `resolver.authorize("seller")` or `resolver.authorize("buyer")`. If you try and invoke these endpoints as an admin, they all need to be changed to `resolver.authorize(["seller", "admin"])` or `resolver.authorize(["buyer", "admin"])` etc. If you assume the role of the user you're impersonating, you don't need to change anything. In terms of security: - `startImpersonating` should only be available to admins, so it should be secured with `resolver.authorize("admin")`. - we can allow `stopImpersonating` to be called without a role restriction as it is: the code already checks if `impersonatingFromUserId` is present in the session. If present, the user simply regains whatever role they had before ("admin", "support", etc), otherwise the endpoint is no-op.
Co-authored-by: Roshan Manuel <Roshan,manuel@angelic-group.com>
Co-authored-by: Roshan Manuel <Roshan,manuel@angelic-group.com> Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: Brandon Bayer <b@bayer.ws>
….mdx (#492) * add some comments to getQueryKey and invalidateQuery * add link to react query docs
…erQuery (#491) * Add usecase "dynamic routing" * Add reference to useParams, useParam and useRouterQuery * typo, move link at useParams and useParam
* add test database to postgres docker docs * clarified that test db must be different than main
Co-authored-by: Roshan Manuel <Roshan,manuel@angelic-group.com> Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Roshan Manuel <31125563+Roesh@users.noreply.github.com> Co-authored-by: Francesco Sardo <francesco.deploy@gmail.com> Co-authored-by: Antony Kamp <tony.kamp@web.de> Co-authored-by: Nikolay <enemycnt@users.noreply.github.com> Co-authored-by: Andreas Thomas <dev@chronark.com> Co-authored-by: Marek Orłowski <16357457+ormarek@users.noreply.github.com>
Co-authored-by: Brandon Bayer <b@bayer.ws>
Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Lukas Neumann <l.neumann@layer9.berlin>
Co-authored-by: Nicolas <ntorres.dev@gmail.com>
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.
This PR was automatically generated.
Merge changes from blitzjs.com at 9a28237
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.