Additional data types and optional configuration in AI Assist v4.0.0

AI Assist now also supports these previously ignored types:

• boolean
• number
• boolean arrays
• number arrays
• slug – Assist will not do uniqueness checks
• url – Assist will try to skip url fields if the instruction does not contain details about what the URL should be
• date
• datetime

This means users can attach instructions to these fields, and they will be written to by default (when in scope of the instruction).

Since language about date and time is time-zone and locale dependent, Assist will now send the browsers timezone and locale as part of the request by default. This allows instructions to use language like "today at noon", and "next year" and still get dates and datetimes as expected.

See the updated README.md and new reference docs on plugin config for details on how to override the default timezone for the current user (assist.localeSettings)

assist({
  //Showing defaults
  assist: {
    localeSettings: () => Intl.DateTimeFormat().resolvedOptions(),
    maxPathDepth: 4,
    temperature: 0.3
  },
})

• localeSettings: See section on date and datetime in the README
• maxPathDepth: The max depth for document paths AI Assist will write to.
• temperature: Influences how much the output of an instruction will vary between runs.

This is a breaking change of the plugin, since it will now visit perviously ignored fields.

Previous versions of the plugin will continue to work with the backend; these new features are enabled through a apiClient api version bump.

Other than bumping the plugin version to 4.0.0 no code changes are strictly needed. However, do note the following changes in behavior:

• fields of the types mentioned above can now have instructions, and will be written to.
• temperature is now 0.3 by default, up from 0. This means that re-runs of the same instruction could see a bit more variance in outcome than before. If this is not wanted, configure the plugin to use temperature 0.