unmangle/cleanup/simplifying. Ready.

[raszpl]

No description provided.

[ImprovedTube]

wouldn't it be nice if settings.js, if it is a GUI template, came almost minified, with similar scroll height as the GUI and strategically placed/manual line breaks or indentation only? (While IDE's could display it the same as now by and intentional/manual line breaks could remain displayed marked up then.)
At least (,said before,) i don't understand why IDEs dont actually support JSON & XML, which could rather be displayed as tree-shaped-spreadsheet-fields.

[ImprovedTube]

youtube/menu/satus.js

Line 3215 in b1b9a41

const included = ['switch', 'select', 'slider', 'shortcut', 'radio', 'color-picker', 'label', 'button'],

Btw, semantically search is missing pathes like Appearance > Details > Buttons (below the player)
& section titles like:

component: 'section',
variant: 'card',
title: 'watchedVideos',

---

#1935 (comment)

[raszpl]

wouldn't it be nice if settings.js, if it is a GUI template, came almost minified

no :) minify is what you do in the deploy phase when make scripts are packaging for release

with similar scroll height as the GUI and strategically placed/manual line breaks or indentation only? (While IDE's could display it the same as now by and intentional/manual line breaks could remain displayed marked up then.) At least (,said before,) i don't understand why IDEs dont actually support JSON & XML, which could rather be displayed as tree-shaped-spreadsheet-fields.

Why would you want unreadable mess in source files? Most IDEs support auto formatting packed JSON. For example Ctrl Alt L in pychrm.

Btw, semantically search is missing pathes like Appearance > Details > Buttons (below the player)

Ill look into that

& section titles like:

component: 'section',
variant: 'card',
title: 'watchedVideos',

this is a section, cant include that, otherwise searching player would display whole contents of player section, search "watched" and you get all three entries