For anyone else working on understanding some of the JS helpers for the Colossal Order UI package, I spent some time deobfuscating a couple functions/classes. Please note there certainly be mistakes and there is some omitted code; however, overall the gist is present.
Upgrading to Pocketbase v23 was a large undertaking due to the amount of fundamental changes to extending as a framework. The library contains several excellent resources, including the GitHub Release and Pocketbase Upgrade Guide, that help with the upgrade. However, they do not explain how to handle upgrading deployed/production instances, which is a bit more tricky depending on the server host. This guide deals with upgrading a Pocketbase application deployed on Pockethost, an excellent and affordable hosting service for Pocketbase apps.
The Pocketbase Upgrade Guide provides an excellent guide to the major breaking changes. However, there were a few assorted changes not explicitly documented (and there may be others still).
Email templa
This file contains hidden or 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
| /** | |
| * Set defined/scalar entity fields from a DTO (only using fields existing on entity) | |
| * | |
| * NOTE: Mutates original value! | |
| * | |
| * NOTE: Skips all non-scalar fields and `undefined` DTO values, which would other wise cause unexpected | |
| * data loss for non-specified or partially provided relation values. However, non-scalar fields | |
| * can be permitted with `allowNonScalarKeys` if specifically handled/provided. | |
| * | |
| * @param options.allowNonScalarKeys - Allows non-scalar keys to be assigned (ie. arrays, objects, etc) |
OlderNewer