Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make deprecator messaging clearer (#125)
The deprecator messaging was confusing when outputting deprecations, especially if one was removed. The way this was written previously it would appear like the deprecator was looping - saying a deprecation was removed and then immediately showing the deprecation. To make the messaging clearer and to distinguish it from a deprecation that is being thrown, put copy around the deprecations. Before: ``` Minitest::UnexpectedError: DeprecationToolkit::Behaviors::DeprecationRemoved: You have removed deprecations from the codebase. Thanks for being an awesome person. The recorded deprecations needs to be updated to reflect your changes. You can re-record deprecations by adding the `--record-deprecations` flag when running your tests. DEPRECATION WARNING: a deprecation warning ``` After: ``` Minitest::UnexpectedError: DeprecationToolkit::Behaviors::DeprecationRemoved: You have removed deprecations from the codebase. Thanks for being an awesome person. The recorded deprecations needs to be updated to reflect your changes. You can re-record deprecations by adding the `--record-deprecations` flag when running your tests. ****** The following deprecations were removed: ****** DEPRECATION WARNING: a deprecation warning ****************************************************** ``` Note that I also fixed a test name where "triggered" was spelled incorrectly.
- Loading branch information