redhat-developer / redhat-developer/vscode-rsp-ui

The property enableAsyncPublish set to true has no effect

Open
#207 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
49
Forks
27
Avg merge
12h 28m
Merged PRs (30d)
7

Description

Hi All,

  1. When I set this configuration:
   "rsp-ui.enableStartServerOnActivation": [
    {
      "id": "redhat.vscode-server-connector",
      "name": "Red Hat Server Connector",
      "startOnActivation": true,
      "rsp-ui.enableAsyncPublish": true
    }
  ]
 VSCode identify the settings and the setting is displayed in light blue and the description of the setting is displayed when I drag the mouse over the setting (it's a little irrelevant but the text is: "Specifies which RSP Server have to be automatically started during activation. If option is disabled, user will have to manually start the RSP Server through command palette or context menu"). 
  1. When I set this configuration:
  "rsp-ui.enableAsyncPublish": true
VSCode does not identify the setting .. the setting is displayed in grayed blue and the text "Uknown Configuration Setting"  is displayed when I drag the mouse over.

Anyway, the server deploys  the application during initialization and not after initialization as defined by the setting. 

Any tips?


OS: Ubuntu
Kernel: 5.11.0-40-generic
VSCode Version: 1.62.3
RSP-ui version: redhat.vscode-rsp-ui-0.23.11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the configuration in VS Code with rsp-ui.enableAsyncPublish set both globally and inside rsp-ui.enableStartServerOnActivation. Compare whether VS Code recognizes each setting and when deployment occurs during server activation. Done means the setting is recognized in its documented form and publishing occurs asynchronously after initialization.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.