1.1.3

• Continuing to improve exception error messages to be more helpful.

1.1.2

• Improved CATEGORISE action parser to handle greater variety of text edge cases (especially comma-separated terms).
• More helpful error messages for TypeError coercion problems where a specified type mismatch occurs.

1.1.1

• Fixes for where source field names include special characters (newlines / tabs) or characters used in scripts. As whyqd is used more this may need thorough review.

1.1.0

• Fixes to tests and bumped to 1.1.0

1.0.9

• Added in new usdate data type which supports automatic date type coersion from US date formats (MM-DD-YYYY).
• New COLLATE action permitting scripts which collate a column-wise list of fields into an ordered array data type.
• Updated all dependencies, which necessitated a bump to the minimum supported Python version being 3.9.
• New tutorial to demonstrate the COLLATE and usdate features.
• Ray settings for initialisation will now be more forgiving. You don't need to provide default values.

1.0.8

• CategoryModel terms now use StrictBool to avoid Pydantic's liberal interpretation of booleans.

1.0.7

• Minor fix, but crucial for continuing ambiguity issue with category terms. Any of source or destination fields or terms can share a name, which causes painful and tedious issues. Hopefully this fix resolves it.

1.0.5

• Additional ambiguity checks for category term edge case where source or destination fields can share category names.

1.0.4

• Dependency updates.
• Permitting nrow limit on Parquet files.
• Disambiguation where schema subject and object field categories have the same name.
• Ambiguity checks for string blank space. If source data includes, should not be removed to preserve original structure.

1.0.1

Minor convenience update.

• Permitting nrow limit on Parquet files.