fixes a bug where flycheck was not showing some warnings for .tsx #157
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.
Full bug discussion here:
#156
Motivation
When developing inside .tsx files, we had missing warnings from flycheck due from some disabling, it looked like we could only (manually) have ts-tide or javascript eslint, not both enabled.
Approach
Inside
frontside-javascript--tsx-web-mode-hook
function we now disable all checkers and then add both'tsx-tide 'javascript-eslint
.Alternate Designs
I am not sure how to do it another way, but this line might be optional:
(setq flycheck-disabled-checkers nil)