[Suggestion] [VSC-Web] HTTP request parameters interoperation

[MasterInQuestion]

    Interpreting HTTP GET (provisionally also POST) parameters to enable certain interoperation:
    E.g. "settings" expecting the settings JSON, applying which to modify current settings.
    .
    This should significantly improve the app's portability. [ Via "https://vscode.dev/?settings=${JSON}" alike. ]


    Some similar but not as critical parameter suggestions:
    /(?:title|text|file|diff)\d*/:
    |*| If "\d" (the optional trailing number) doesn't exist: assume 0.
    |*| The /\d+/ must be unique for each tab. (e.g. no "file0" and "text0" at the same time)
    |*| "title", "text": Correspondingly set the new files' title and content (text). [1]
    |*| "file": The URI of files [2] to open.
    |*| "diff": Diff views comparing the tabs to open (identified by the unique /\d+/). Expected input: /\d+,\d+/ (comma separated numbers).

[1] When a "title" defined without corresponding "text": assume empty "text".
[2] Perhaps also internal tabs (e.g. "Settings" tab).

[Tyriar]

I don't understand what the request is?

[MasterInQuestion]

    Much similar to what mentioned in [ https://code.visualstudio.com/updates/v1_75#_profiles ].
    But more effective and reliable (for VSC-Web).

    Related: #116740

    ----

    If "the request" you mean is HTTP request:
    In simple words, most web requests are HTTP requests: for example, accessing the VSC-Web through [ https://vscode.dev/ ].