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.
I have added a Base64 inferer in the formats folder. A given string is simply checked against a regex. It accepts all base64 allowed signs and includes the trailing =-sign as padding.
Important:
How I see it every alphanumeric string could basically be base64 if the length is correct. This would lead to the problem that nearly every string could possibly be infered as base64 eventhough it is a normal string.
A solution would be to exclude this inferer generally and to let any library user explicitly include it in the list of used inferers if needed.