Detect fields using base64 URL encoding #507
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some fields are encoded as base64 URL instead of Base64 Standard. This tries to catch fields requiring URL encoding by searching the description for specific words.
I'm not happy with the current implementation but I'm not too familiar with Python. Any suggestions on how to avoid the
description
parameter onserde_as
?This resulted into the following diff:
Fixes #496