Issue #17487: Add ECMAScript6BestPractices#18158
Conversation
d27dbf2 to
ed6643c
Compare
ed6643c to
0615198
Compare
ECMAScript6BestPracticesECMAScript6BestPractices
0615198 to
d71b00a
Compare
|
nice to see rewrite also fixing .js stuff as well.
|
a6cec70 to
8899e60
Compare
|
item |
ECMAScript6BestPracticesECMAScript6BestPractices
27b8bfd to
ed9d2fb
Compare
|
wait for enabler, thx. |
|
tryout pipeline with this, reopen. |
be16a73 to
0fa1c73
Compare
|
IO: [ERROR] exceptionMessage: "Connection refused" |
ECMAScript6BestPracticesECMAScript6BestPractices
0fa1c73 to
876727a
Compare
|
@smita1078 , @stoyanK7 , do you agree with such js updates? |
I’m okay with these JS updates. Even if the current behavior is unchanged, better to handle them in a separate PR |
|
@smita1078 , if you think that some update should not be done, please state it and we will not do it. We show do update only if it is beneficial. |
yes of course this is considered benefit as smallest scope possible always the best. If not possible to use let this something is an issue or an valid ignore.
yes then undo. |
876727a to
ac9ccad
Compare
After actually considering the code, most of the mutability turned out to be obsolete, as usual, so Everything else has been boiled down to a minimal version, avoiding unnecessary coupling and promoting cohesion instead. |
| } | ||
|
|
||
| var name = anchorItem.previousSibling.previousElementSibling.id; | ||
| var link = "" + url + "#" + name + ""; |
| } else { | ||
| name = anchorItem.childNodes[0].name; | ||
| } | ||
| var link = "" + url + "#" + name + ""; |
Agreed!, I think keeping strict mode avoids unnecessary risk. Better to not remove it. Thanks |
ac9ccad to
e27dc44
Compare
e27dc44 to
f9a106a
Compare
|
@smita1078 , please help to review this PR. if you notice that this is no good direction, we can close this PR. JS is not primary in our repository, some not-perfect code is ok. |
its not non perfect is has worst quality possible. Its just working (by accident) just like the remaining code base, how needs this silly thing? |
@romani I don’t think the discussion was moving in a productive direction anymore. From a review perspective, I also don’t think this change is needed right now since JS isn’t a primary focus for us. |
For me this text lacks a detailed explanation for why something is neither this nor that. It merely repeats the Romani excuse and fails to focus on the matter. |
|
All changes should have clear definition of problem and clean and exact fix. Reviewers should see all clearly. |


Issue #17487: apply
ECMAScript6BestPractices