Adding compilation option for all client libraries.#1700
Adding compilation option for all client libraries.#1700sakshi-arora1 wants to merge 1 commit intodevfrom
Conversation
There was a problem hiding this comment.
@sakshi-arora1 - I am not sure this does what you want it to.
When precompiling client libraries during a full stack pipeline execution we use closure compiler v20210106 .
Looking at the source code I don't see ECMASCRIPT_2021 as a valid option for languageIn - https://github.com/google/closure-compiler/tree/v20211006 .
Sets the language spec to which input sources should conform. Options: ECMASCRIPT3, ECMASCRIPT5, ECMASCRIPT5_STRICT, ECMASCRIPT_2015, ECMASCRIPT_2016, ECMASCRIPT_2017, ECMASCRIPT_2018, ECMASCRIPT_2019, STABLE, ECMASCRIPT_NEXT
Accessibility Violations Found
|
Accessibility Violations Found
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
rismehta
left a comment
There was a problem hiding this comment.
We should just add it for editor specific client libraries, since runtime client libraries are always included via runtime.all which already has this.
But, its upto customer they way they wish to include these individual client libs. Do you see any harm in putting this on each clientlib? |
Let's just fix the original issue for now to keep the impact minimal |
But how will this impact anything? |
Hi @rombert , that is correct, I looked up and it seems ECMASCRIPT_2021 was introduced in version v20211107 [1]. |
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: