Bump pocketbase from 0.19.0 to 0.21.2

[dependabot]

Bumps pocketbase from 0.19.0 to 0.21.2.

Release notes

Sourced from pocketbase's releases.

v0.21.2 Release

• Exported HealthService types (#289).

v0.21.1 Release

• 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.

• Fixed the fetch mock tests to check also the sent body param values.

• Formatted the source code with prettier.

v0.21.0 Release

⚠️ 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.

v0.20.3 Release

• 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).

v0.20.2 Release

• Throw 404 error for getOne("") when invoked with empty id (#271).

• Added @throw {ClientResponseError} jsdoc annotation to the regular request methods (#262).

v0.20.1 Release

• Propagate the PB_CONNECT EventSource message to allow listening to the realtime connect/reconnect events.

  pb.realtime.subscribe("PB_CONNECT", (e) => {
    console.log(e.clientId);
  })

... (truncated)

Changelog

Sourced from pocketbase's changelog.

0.21.2

• Exported HealthService types (#289).

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.

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.

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).

0.20.2

• Throw 404 error for getOne("") when invoked with empty id (#271).

• Added @throw {ClientResponseError} jsdoc annotation to the regular request methods (#262).

... (truncated)

Commits

• 04f9ae5 updated changelog
• 01eda0c bumped package version
• b0c4d26 #289 exported HealthService interfaces
• 09f38c5 updated CHANGELOG
• 73ed625 bumped package version
• c04b264 updated dev deps and added prettier
• 05cac8a manually update the matching current AuthStore record verified state on succe...
• 2fb8de9 bumped package version
• 9f25a9f use PocketBase v0.21 jsonPayload multipart/form-data field when sending mixed...
• fd15854 gracefully handle oauth2 redirect error
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)