-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Better validation of Dataset URI during dag parse #26389
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
Conversation
1e31a24 to
bb9c320
Compare
|
Might be worth retiring |
I considered that, but we do still have validation on the model -- should we keep that or not? |
|
Oh, those are testing the public dataset class (after the refactor the test got changed, but not the location), not the model. Yeah I'll remove those tests! |
bb9c320 to
6d3c333
Compare
ce9e374 to
5038bf4
Compare
|
Fail Ash. (New dev env, don't have pre-commit set up there yet) |
Previously we had the validation on the Dataset model, but we since moved the "dag" facing class to a separate one. This adds validation to the public class, and extends the validation to not allow space-only strings
5038bf4 to
c74dfb6
Compare
|
The failure is due to #26382 I think -- where we forgot to add it to rat_exclude? |
Yep, unrelated to this one. |
|
Failure is on main, merging. |
|
#26396 to fix main. |
Previously we had the validation on the Dataset model, but we since moved the "dag" facing class to a separate one. This adds validation to the public class, and extends the validation to not allow space-only strings (cherry picked from commit bd181da)
Previously we had the validation on the Dataset model, but we since moved the "dag" facing class to a separate one. This adds validation to the public class, and extends the validation to not allow space-only strings
Closes #26380