Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There are minor coding standards violations that should be addressed before Settings Tray is marked as stable. This fixes them. 👏🤷♀️
These coding standards violations would usually be done in general patch instead of per file but since this currently experimental code it seems logic to fix these before marking the code as stable. @see #2922603: Mark Settings Tray module as stable
Comment | File | Size | Author |
---|---|---|---|
#5 | interdiff-2924351-2-5.txt | 5.06 KB | GrandmaGlassesRopeMan |
#5 | 2924351-5.patch | 3.18 KB | GrandmaGlassesRopeMan |
#2 | 2924351-2.patch | 1022 bytes | GrandmaGlassesRopeMan |
Comments
Comment #2
GrandmaGlassesRopeManThere are no actual changes to the transpiled code. ✌️
Comment #3
xjmI will create a separate issue to re-wrap the comments in the file (since there are more). Meanwhile we can remove this hunk from the patch.
Comment #4
xjm#2924365: Wrap JS comments in Settings Tray to 80 character limit is in now so this can be rerolled on top of that.
Comment #5
GrandmaGlassesRopeMan- removes 80 character wrapping adjustments
- fixes multiline comment format
- removes use of
in
operatorComment #7
dawehnerIn general I'm a bit confused ... the entire point of automatic code style checking using our special eslint file is not have these special fix patches,
but now we are okay with having a special case? Maybe we should update the issue summary why this is the way to go.
I am a bit confused about the use of hasOwnProperty given that https://eslint.org/docs/rules/no-prototype-builtins exists
Comment #8
GrandmaGlassesRopeMan@dawehner Yes. I agree this is a special case. Perhaps we can update the issue summary to reflect that? Additionally, we've set
"no-prototype-builtins": [0]
in our existing eslint file. I think once we are done with the coding standards cleanup, we can remove this, however currently we are not doing anything withSet
orMap
.Comment #9
tedbowUpdate summary re #7 and #8
Comment #11
tedbowI don't actually see the new test failure. The last #5 failed was 11/20 and it just passed yesterday 12/13
Comment #13
tedbowSetting back to RTBC because DrupalCI memory problem
Comment #15
tedbowSetting back to RTBC because DrupalCI memory problem
Comment #17
GrandmaGlassesRopeManComment #19
GrandmaGlassesRopeManComment #20
webchickGreat, let's get this sucker in!
Committed and pushed to 8.5.x. Thanks!