[WIP] Post-processing effects for FURY Effects API #850
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
JoaoDell
changed the title
Codecov Report
@@ Coverage Diff @@
## master #850 +/- ##
==========================================
- Coverage 84.49% 83.19% -1.30%
==========================================
Files 44 45 +1
Lines 10454 10618 +164
Branches 1411 1416 +5
==========================================
+ Hits 8833 8834 +1
- Misses 1252 1415 +163
Partials 369 369
|
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.
Hello, this is a draft PR that aims to implement some other post-processing effects to the FURY Effects API. Currently, this is basedon the old API version and shall be updated as soon as I have the time to do it, but I have decided to create this draft PR anyway to keep track of the work and keep everyone updated.
The current effects this PR introduces are: