Skip to content

[24.2] Fix correctness of assertion validation in new linter. #19203

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

Closed

Conversation

jmchilton
Copy link
Member

We were using the YAML linters which were more strongly typed to validate the XML without a lot of processing - including no type conversion. Fixing this found some other problems also. Huge thanks to @bernt-matthias for reporting the issue - #19197 (comment).

This just fixes the correctness. We still probably need a way to improve the pydantic output for these validation errors.

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@jmchilton jmchilton marked this pull request as ready for review November 29, 2024 20:30
@github-actions github-actions bot added this to the 25.0 milestone Nov 29, 2024
@mvdbeek mvdbeek modified the milestones: 25.0, 25.1 May 13, 2025
@jmchilton
Copy link
Member Author

I don't recall the difference between this and #19715 - but that one was merged so I will assume it was the right fix. I'm always so distracted.

@jmchilton jmchilton closed this May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants