v0.3.9 - The one with (slightly) smarter transforming of PII

[justinvdm]

In this release, we now account for your column types when detecting PII and determine which replacement value to use.

Case 1: Accounting for column types when detecting PII

For example, let’s say you had a column with the name token, which was a bool postgres column. Previously, the example transform.ts config would end up with something like the following:

const config = () => ({
  public: {
    SomeTable: ({ row }) => ({
      // Here, `token` is a `bool`, but we were generating a string uuid value
      token: copycat.uuid(row.token)
    })
  }
})

In this release, we would no longer identify token as PII, since it is a bool field, and so we also wouldn’t add an example transformation for it in your transform.ts.

Case 2: Accounting for column types when replacing values

Lets say you had a latitude column of type float. Previously, we would provide a string value as an example in your transform.ts, regardless of the fact that the column was float or not. In this release, we will only generate a string if the column is a string column (e.g. text), and and only generate a number if it is a number column (e.g. float):

const config = () => ({
  public: {
    SomeTable: ({ row }) => ({
      latitude: copycat.float(row.latitude, { min: -90, max: 90 })
    })
  }
})