Added example for working with SwiftUI #260
Open
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
Codecov Report
@@ Coverage Diff @@
## master #260 +/- ##
=======================================
Coverage 91.31% 91.31%
=======================================
Files 60 60
Lines 1059 1059
=======================================
Hits 967 967
Misses 92 92 Continue to review full report at Codecov.
|
This was referenced Jun 1, 2021
Closed
Closed
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 suggest adding an example of working with SwiftUI to
Down-Example, because people are starting to switch to it and the need is growing (at one time, I myself asked a question about this in the issues 馃槉)This example demonstrates working with
DownViewand withDown.toAttributedStringP.S. - Attribute line down by default uses the standard Styler class, so until PR #258 is adopted no images will be displayed