#V13 Final Deprecations

1 messages · Page 1 of 1 (latest)

clear sapphire
#

Hello <@&596076164104323104> please see the following list of functions, properties, or workflows which were deprecated prior to V13 where their compatibility warning period is expired.

These all go from being soft-breaking changes (where the old functionality continued to work, but with a warning) to hard-breaking changes where the old functionality no longer works at all.

https://github.com/foundryvtt/foundryvtt/issues/11815

Please bear in mind that we are still in the Prototype (and soon API Development) phase of V13 dev, so the window for feedback here is absolutely open if there are any of these changes that are giving you specific concern, let us know!

#

The PR was.... satisfying

image.png
#

Also please note that this is a subset of the breaking changes in V13. This focuses specifically on prior deprecations which have reached the end of their compatibility arc.

For the full list of breaking changes that we are tracking, refer to the "Breaking Changes" tab of our V13 project board: https://github.com/orgs/foundryvtt/projects/58/views/8

slim osprey
#

Didn't see this in the list, but I've gotten reports that NeDB compendiums in modules don't work anymore in V13.

clear sapphire
silver vortex
#

The deprecation issue lists ClientDocument#_createEmbeddedDocuments etc. as deprecated. I think those are supposed to be the _pre and _on methods.

topaz field
#

do we have a list of new deprecations?

clear sapphire
clear sapphire
#

Although I think this project board view currently understates the significance of a few changes in particular which we need to work to document more emphatically:

  1. Many (most?, all?) applications are moving to ApplicationV2 which can cause breaking changes for subclasses or hooks that interact with that application.
  2. ThemeV2 is now the default and forced CSS structure along with layers and some new CSS conventions. We have done what we can to shield modules and systems from these changes because package-defined CSS gets wrapped in a layer that takes precedence over our core layers, but there may still be some unexpected layout shifts.
  3. All Token movement now uses movement waypoints instead of direct {x, y, elevation, etc...} updates. These direct updates are automatically re-interpreted into waypoints but modules which are manipulating token movement within a preUpdate or onUpdate hook will be impacted and need to change their approach.
whole parrot
#

I assume this means that passing the parameter is deprecated in v11 rather than saying fromUuidSync is deprecated?

"Passing a relative document as the second parameter in fromUuid(uuid, relative) is deprecated and you must pass it as athe relative key in optionsas fromUuid(uuid, {relative}) instead. This also applies to fromUuidSync (deprecated in v11)"

clear sapphire
onyx turret
#

Is there a priority list we can see for approximate likelihood of what apps might not be migrated?