v0.8.0 - The one where character limits are too legit to quit

[justinvdm]

In this release, we've made a change to how we generate your .snaplet/transform.ts config: for columns that we think have PII in them that also have character limits (e.g. varchar(16)), we will now use copycat.scramble() instead of a different copycat method:

const config: Transform = () => ({
  public: {
    customer({ row }) {
      return {
        email: copycat.scramble(row.email, {
          preserve: ["@", "."],
        }),
        first_name: copycat.scramble(row.first_name),
        last_name: copycat.scramble(row.last_name),
      };
    },
  },
});

This means that if your original values were within some character limit, the replaced values will still stay within those character limits. It also does mean you'll see values that look more like [email protected] and less like [email protected]. You can always change back to using the original copycat methods (e.g. copycat.email()) if this suited your needs better. And of course, any feedback on this change would be very welcome!

If your columns do not have character limits (e.g. if you have a text column), then the original behaviour will remain the same (e.g. in the case of emails, we'll generate copycat.email(row.email)).

A note for existing projects: if you already have a transform.ts in your project and would like to have them updated to use this new behaviour, you can run the following to generate a new example transform.ts (note that it will replace everything in your current transform.ts though!):

snaplet config generate -t transform