The NoStatus parameter (and DefaultNoStatus config value) were deprecated as part of #253 when we stopped showing status except for multi-page requests that exceeded some minimum number of pages.
At that time, NoStatus (and DefaultNoStatus) were not removed in order to minimize the churn to the module. However, keeping it in is adding unnecessary complexity to the module as we continue to expand what the module can do.
This change removes NoStatus (and DefaultNoStatus) from the module entirely. The only impact that this may cause is with users who are currently using one (or both) of them. This breaking change impact should be minimal, but its best for the breaking change to be part of the coming release which already has a number of other breaking changes as well, as opposed to having more breaking changes in a successive release.
Issues Fixed
n/a
References
n/a
Checklist
[x] You actually ran the code that you just wrote, especially if you did just "one last quick change".
[x] Comment-based help added/updated, including examples.
[x] Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.
[x] Relevant usage examples have been added/updated in USAGE.md.
Description
The
NoStatus
parameter (andDefaultNoStatus
config value) were deprecated as part of #253 when we stopped showing status except for multi-page requests that exceeded some minimum number of pages.At that time,
NoStatus
(andDefaultNoStatus
) were not removed in order to minimize the churn to the module. However, keeping it in is adding unnecessary complexity to the module as we continue to expand what the module can do.This change removes
NoStatus
(andDefaultNoStatus
) from the module entirely. The only impact that this may cause is with users who are currently using one (or both) of them. This breaking change impact should be minimal, but its best for the breaking change to be part of the coming release which already has a number of other breaking changes as well, as opposed to having more breaking changes in a successive release.Issues Fixed
n/a
References
n/a
Checklist
Formatters were created for any new types being added.New/changed code continues to support the pipeline.Changes to the manifest file follow the manifest guidance.Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.Relevant usage examples have been added/updated in USAGE.md.If desired, ensure your name is added to our Contributors list