feat!: add optional flatbuffer_verifier_options parameter to methods
#36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ev3nvy
added
type: feature
BREAKING CHANGE: adding/removing parameters on public functions is semver-MAJOR change
ev3nvy
force-pushed
the
verifier-opts-param
branch
from
781da46 to
40e8d98
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added an optional
flatbuffer_verifier_optionsparameter of typeOption<&flatbuffers::VerifierOptions>toRiotManifest::from_path,RiotManifest::from_readerandManifestData::parse. If set toNone, it defaults tomax_tables:10_000_000+ defaults.Motivation
Latest riot manifest
00AFF46430CFBC0Cdoesn't parse with theFlatbufferError(TooManyTables)error.