In T301128: research: Understand how current and new users of Growth features would be affected by switching to Vue we analyzed and discussed ES6 browser compatibility and Growth features.

In T301128#7995103, @Sgs wrote:

What do you think about dropping IE11 support from next fiscal year on GrowthExperiments features? @MMiller_WMF @kostajh

The analysis here makes me feel confident in dropping IE11 support in GrowthExperiments features and moving forward with Vue migration of our code. @KStoller-WMF, could you please have a look and let us know your thoughts as well? Then we could mark this task as resolved.

In this task, we can tag patches needed for e.g. adjust linter configuration to assume ES6 for all code in the modules directory.

Acceptance Criteria

1. Use ES6 code in all files in the modules directory for GrowthExperiments
2. ....

Completion checklist

Functionality

• The patches have been code reviewed and merged
• The task passes its acceptance criteria

Engineering

• There are existing and passing unit/integration tests
• Tests for every involved patch should pass
• Coverage for every involved project should have improved or stayed the same

Design & QA

• If the task is UX/Design related: it must be reviewed and approved by the UX/Design team
• Must be reviewed and approved by Quality Assurance.

Documentation

• Related and updated documentation done where necessary
  • Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
  • Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on Extension:GrowthExperiments or Extension:GrowthExperiments/Technical documentation pages.