Skip to main content

About deprecations

"Deprecated" refers to functionality or components that are in the process of being replaced by newer ones or being removed entirely.

Example: Deprecation can affect something as small as a single component prop (label renamed to newlabel), or it can affect an entire component or feature.

Functionality can be deprecated because:

  • It will be superseded by new functionality.
  • The functionality might not align with Jutro's long term vision/roadmap.

Deprecated means something won't work anymore?​

No.

Deprecation means that all of the current functionality works unchanged and you can continue to use it without any code modification, but it will not receive new feature updates. Also, when you use a deprecated component or feature, you will see a warning message in dev mode.

How do I know something has been deprecated?​

We include this information in the following:

  • The release notes identify deprecated functionality.
  • The IDE schema and auto suggestions indicate what has been deprecated.
  • Console warnings.
  • Code itself.
  • Storybook documentation identifies deprecated component properties.
  • Storybook displays a "Deprecated" label next to components that have been deprecated.

What do I do when something is deprecated?​

No immediate action required.

When a deprecation affects an application, you can decide when to adopt the suggested alternative, but everything will still work, so this can be planned and executed at a later stage. Migrate to the alternative as soon as practical to use new features and stay aligned with best practices and current versions.

When something is deprecated, there might be different alternatives provided:

  1. A new component or function is available. Use the new feature instead of the deprecated one. In some cases, codemods can simplify the migration.

  2. Replaced by a pattern. In the case of components, the alternative might be to use a provided pattern and customize it for project requirements.

  3. No alternative provided. In some cases, no alternative is required. This can happen because the functionality is obsolete or outside the library scope. In this case, if still needed, consumers can decide whether they prefer to implement it as part of their project or ask the Guidewire team to hand over the current code.

What's the support timeline for deprecated functionality?​

  • Deprecations can happen in any minor or major release.
  • Decommissions can happen in any major release.
  • Functionality is deprecated only when an alternative or guidance is available (unless no alternative is considered necessary).
  • There is no fixed period between deprecation and decommission. Deprecated functionality is considered for decommission only when its usage is minimal or its removal is planned, and affected consumers are engaged directly beforehand.

What does "support" mean for a deprecated functionality?​

Deprecated functionality, such as a component, function, package, or a single component property, continues to work but receives no new features. While it is still shipped, Guidewire:

  • fixes security vulnerabilities;
  • fixes accessibility issues against the accessibility conformance level that applied when the functionality was deprecated; deprecated functionality is not raised to newer conformance levels;
  • reviews and prioritizes any other reported issue case by case, and releases accepted fixes in a future minor version.

This commitment lasts as long as the functionality is available in the platform. For the full phase-by-phase model, including how support narrows over time, see API deprecation and decommission policy.