Lines Matching refs:deprecation

353 undergo deprecation. The exceptions to this rule are:
415 documentation must state the deprecation status.
418   * A deprecation notice appears in the API documentation.
422   * Might cause a runtime warning with the [`--pending-deprecation`][] flag or
427   * If used with the [`--throw-deprecation`][] flag, will throw a runtime error.
446 warnings, and errors use the identifier when referring to the deprecation. The
447 documentation for the deprecation identifier must always remain in the API
448 documentation. This is true even if the deprecation is no longer in use (for
451 <a id="deprecation-cycle"></a>
464 deprecation lands on the master branch.
467 deprecation level of an API.
919 [`--pending-deprecation`]: ../api/cli.md#--pending-deprecation
920 [`--throw-deprecation`]: ../api/cli.md#--throw-deprecation