Allow empty string as valid URL in DCR workflow#987
Conversation
domdomegg
left a comment
There was a problem hiding this comment.
I may be wrong, please push back if so. But I think we might want to allow empty strings only on properties that are not required.
E.g. we should not allow empty string for token_endpoint. But we should allow it for op_tos_uri.
Maybe more broadly - potentially back to the issue - is should we really be accepting an empty string? Should the endpoints just not be returning anything for this property, which is already allowed by the .optional()?
daf1ea5 to
f2ffcbd
Compare
|
Thanks for your review @domdomegg. I updated my PR with a few modifications that might address some of your concern :
Maybe this new schema could be removed during next protocol version release in November in order to keep it contained within a certain time frame |
|
Hey @pcarleton - sorry for the ping, any chance this can get merged :)? |
Fixes #940
Motivation and Context
Allow empty URL as valid URL in DCR payload
How Has This Been Tested?
Added a specific test case for empty string
Breaking Changes
None, this actually reverts breaking change introduced by #877
Types of changes
Checklist
Additional context