Add support for Path.Data from string and resources #698
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
dr1rrb
approved these changes
Mar 19, 2019
jeromelaban
force-pushed
the
dev/jela/path-data
branch
from
0293629 to
f0f34f3
Compare
carldebilly
added a commit
that referenced
this pull request
Mar 22, 2019
(rollback PR #698 for Wasm)
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Using a string static resource to set a
Path.Dataproperty fails a conversion.What is the new behavior?
It is now possible to use a static resource string to set a
Path.Data.PR Checklist
Please check if your PR fulfills the following requirements: