docs: update directive example with correct picture output interface#882
Open
juliendargelos wants to merge 1 commit into
Open
docs: update directive example with correct picture output interface#882juliendargelos wants to merge 1 commit into
juliendargelos wants to merge 1 commit into
Conversation
|
Collaborator
|
The docs are generally auto generated so probably you need to find where this is coming from |
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
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 written new tests, as applicable (for bug fixes / features)Not applicableDocs have been added / updated (for bug fixes / features)Not applicableI have added a changeset, if applicableNot applicableWhat kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Update directive example with correct picture output interface and valid html.
What is the new behavior (if this is a feature change)?
Not applicable
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information:
None