Skip to main content

Legacy package

The purpose of @jutro/legacy package is to contain deprecated features for their long term availability before they are decommissioned. It might be considered as the last step of a feature life cycle before its removal, especially for those deprecated features that need to be maintained in the library for a long period. However, this is not a mandatory step, and deprecated features might be decommissioned without being previously moved to @jutro/legacy. Please note that no special consideration regarding maintenance or support is given to this package, the same rules as for any other deprecated feature apply.

When is a feature moved to the legacy package?​

The following considerations are applied to move a feature to @jutro/legacy:

  1. Only deprecated features can be moved to the @jutro/legacy package
  2. Move to @jutro/legacy it is considered a breaking change. This is because the dependency and import statements would be modified
  3. There is no specific time frame defined between the deprecation of a feature and its moving to @jutro/legacy
  4. Whenever possible, an automated helper (known as a codemod) is provided to facilitate the code update

When is a feature decommissioned after it is moved to the legacy package?​

No target date or specific availability period is defined. The decommission step will depend on usage and alternatives and it will be reviewed case by case.

Can I use features from the legacy package?​

As every feature under the @jutro/legacy package is deprecated, application developers are encouraged to avoid the usage of these features or to ensure that the migration from them to their alternative is considered and planned.

Any application already using a feature from @jutro/legacy package can continue using it, but it is recommended that migration is planned. See the What do I do when something is deprecated section for more details. For new applications, avoid using @jutro/legacy features. Guidewire might include some verifications or access restrictions on @jutro/legacy package usage, so while existing customers who are already relying on these features will have access, new applications might be prevented from using them.

If the alternative to a deprecated feature cannot be identified, you can reach out to Guidewire for support.