Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catch warnings in tests & remove support for older URLFor argument syntax #253

Merged
merged 2 commits into from
Feb 6, 2023

Conversation

sirosen
Copy link
Collaborator

@sirosen sirosen commented Feb 6, 2023

I've rebased this off of #243 to pick up the latest changes and resolve conflicts and added an additional changeset. My added change sets filterwarnings = error and deals with the consequences of that setting.


Apply filterwarnings = error to tests and update

This applies the error filter to force test failures on warnings, and does the necessary cleanup. Primarily, that means identifying the two classes of ignore: rules which are necessary to handle cases outside of this library's control. Secondarily, it forces the deprecation of the older url_for field specification syntax, which cannot be supported cleanly. Since this was deprecated in the last release, it is presumably safe to remove it, but the change is still noted as breaking in the changelog.

GabrielLins64 and others added 2 commits February 6, 2023 04:22
This applies the error filter to force test failures on
warnings, and does the necessary cleanup. Primarily, that means
identifying the two classes of `ignore:` rules which are necessary to
handle cases outside of this library's control. Secondarily, it forces
the deprecation of the older url_for field specification syntax, which
cannot be supported cleanly. Since this was deprecated in the last
release, it is presumably safe to remove it, but the change is still
noted as breaking in the changelog.
@sirosen sirosen merged commit 3faf8c4 into marshmallow-code:dev Feb 6, 2023
@sirosen sirosen deleted the catch-warnings-in-tests branch February 6, 2023 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants