Add exclude field to MultipleEmitters rule. #122
Closed
+33
−1
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.
Hi! Please consider the possibility of adding a field exclude to the MultipleEmitter rule.
I ran into a situation when I have composable function which is always called inside Column, but it is not ColumnScope extension. Like this:
I would not like to change it to
ColumnScope.Ui()
and fix it throughout the project.It would be nice to just exclude
Ui
method from rule checking.Maybe there are some other cases. Anyway it seems pretty flexible.
What do you think about it?