Joseph

As of v10, Data Fields and Data Models are both valid options for types.

@LukeAbby DocumentTypeField is the biggest *blocker* of all of these because it's a StringField extension that's used by the big document types like Actor and Item.

After `toInput` is implemented, update the `formInput` and `formGroup` handlebars helpers in `src/foundry/client/apps/templates.d.mts`

TODO after `0f58b4f3f1a15b12dd431a2385d6f0faede1514a` - [x] Consider extracting the callback on `DataFieldOptions["validate"]` to a `DataFieldValidator` callback as defined by Foundry (possibly `DataField.Validator`?) - [x] Implementation of Form Field helpers needs improvement

UI pitch: Add it as a tooltip, with the duration and source info for if it's favorited

Update `src/foundry/client/pixi/groups/effects.d.mts` after CanvasDarknessEffects is defined.

Update PrimaySpriteMesh when TextureAlphaData is defined

Weren't there a number of fields changes and declarations? Is this just working around that?

> One question though is whether the `data` that gets passed to all the migration methods should really be a `Record` vs `AnyObject`. I think the answer is yes but...

Apologies for delays been busy with handling all the D&D updates