lex and lexgen: Allow encodings in Lexicon files to be arrays of strings #1107
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.
As per bluesky-social/atproto-website#426 and bluesky-social/atproto#3986, this PR adds initial support for arrays of encodings in Lexicon files. See the following example:
In essence, this PR stops
lexgen
from emitting errors when an array of encodings is found in a Lexicon file. This feature is currently of no use to the Go codebase, as Lexicons used here all have only a single encoding. That said, it ensures interoperability should bluesky-social/atproto-website#426 get approved.