v4.3.0: Using Foundry Type Data Model

TLDR: This is strictly an architectural change with no new user-facing features. Probably not worth updating to this specific version if you don't need to (such as Using Foundry v13+.)

What's Changed

• Implementing Type Data Models for all items and actors, which was introduced in Foundry v10
• One of the main features of using these data models is data validation. This means that if a field for an item or actor isn't of the correct type, it will error and not allow you to use it (for example, trying to use a letter for an Essence score instead of a number). In theory, users should not notice any changes. We generally restrict these types of values in the actor/item sheets, such as using inputs that only allow numeric characters, but we can't guarantee with 100% certainty that all user-created documents will pass the validations. Because of this, please update with caution.

Pull Requests

• template.json -> Data Model by @phildominguez in #647
• Compendium to data model by @JFranklin3000 in #665
• v4.3.0 - Merging beta into main by @phildominguez in #666

Full Changelog: v4.2.4...v4.3.0