pocketbase
Advanced tools
Changelog
0.21.4
requestKey
handling in authWithOAuth2({...})
to allow manually cancelling the entire OAuth2 pending request flow using pb.cancelRequest(requestKey)
.
Due to the window.close
caveats note that the OAuth2 popup window may still remain open depending on which stage of the OAuth2 flow the cancellation has been invoked.Changelog
0.21.3
atob
polyfill for ReactNative until Expo 51+ and React Native v0.74+ atob
fix get released.Changelog
0.21.1
Manually update the verified state of the current matching AuthStore
model on successful "confirm-verification" call.
Manually clear the current matching AuthStore
on "confirm-email-change" call because previous tokens are always invalidated.
Updated the fetch
mock tests to check also the sent body params.
Formatted the source and tests with prettier.
Changelog
0.21.0
⚠️ This release works only with PocketBase v0.21.0+ due to changes of how the multipart/form-data
body is handled.
Properly sent json body with multipart/form-data
requests.
This should fix the edge cases mentioned in the v0.20.3 release.
Gracefully handle OAuth2 redirect error with the authWithOAuth2()
call.
Changelog
0.20.3
Partial and temporary workaround for the auto application/json
-> multipart/form-data
request serialization of a json
field when a Blob
/File
is found in the request body (#274).
The "fix" is partial because there are still 2 edge cases that are not handled - when a json
field value is empty array (eg. []
) or array of strings (eg. ["a","b"]
).
The reason for this is because the SDK doesn't have information about the field types and doesn't know which field is a json
or an arrayable select
, file
or relation
, so it can't serialize it properly on its own as FormData
string value.
If you are having troubles with persisting json
values as part of a multipart/form-data
request the easiest fix for now is to manually stringify the json
field value:
await pb.collection("example").create({
// having a Blob/File as object value will convert the request to multipart/form-data
"someFileField": new Blob([123]),
"someJsonField": JSON.stringify(["a","b","c"]),
})
A proper fix for this will be implemented with PocketBase v0.21.0 where we'll have support for a special @jsonPayload
multipart body key, which will allow us to submit mixed multipart/form-data
content (kindof similar to the multipart/mixed
MIME).