Interpret explicit undefined engine option value as "dot"#393
Merged
Conversation
Passing undefined for the engine render option would previously result in a RuntimeError or similar. Instead, the default of "dot" should have been used.
This would only happen if the options object actually had an entry for "engine" with the value undefined. For example, the engine might be determined by the value of a select element.
render(src, {}) // default "dot" engine used
render(src, { engine: undefined }) // unlikely that the API would be used this way, would throw
render(src, { engine: parseEngine(...) }) // more likely, would throw if parseEngine returned undefined
mdaines
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses #386