[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-54119 ESlint rules are not applied on the client Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy started work on JENKINS-54119 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54119
ESlint rules are not applied on the client
Change By:
Baptiste Mathus
h3. Problem statementSince the typescript migration on the evergree-client, we still apply ESLint, but it's a no-op. (I suppose it's looking for .js, and there's none anymore).h3. Expected behaviorESLint should either be ditched on the client side, or enabled through some intermediate tooling (there are apparently a few initiatives around this like https://github.com/eslint/typescript-eslint-parser or even https://palantir.github.io/tslint/) I think this issue is more than trivially important since ESLint, and {{make lint}} for our case, gives a false sense of consistency preservation, when actually now ESLint is basically ignored for the client side.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54119 ESlint rules are not applied on the client Change By: Baptiste Mathus Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54119 ESlint rules are not applied on the client Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-17 08:55 Labels: technical-debt Priority: Major Reporter: Baptiste Mathus Problem statement Since the typescript migration on the evergree-client, we still apply ESLint, but it's a no-op. (I suppose it's looking for .js, and there's none anymore). Expected behavior ESLint should either be ditched on the client side, or enabled through some intermediate tooling (there are apparently a few initiatives around this like https://github.com/eslint/typescript-eslint-parser or even https://palantir.github.io/tslint/) Add Comment
