Disabling compose kotlin checks #356
Closed
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
|
#355 seems like the way to go for me. I'll add my reasoning on that PR. |
|
I think we're aligned on this...so I'm closing. Reopen if we want to continue discussing. Thanks @LikeTheSalad for putting together both options to compare/contrast. ❤️ |
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.
Option to avoid these kinds of issues.
This option disables compose's kotlin checks, although the config to do so is not well documented (it's mostly properly "officially" mentioned here) - Although it seems like it might change in the future. The good thing about this approach though is that it's the one that requires the least amount of changes to work.
Another option is: #355