Test static status bar contributions

[jrieken]

Refs: #167874

• anyOS @bpasero
• anyOS @ulugbekna
• anyOS @devinvalenciano

Complexity: 3

Create Issue

---

Status bar items can now be contributed statically, from package.json. Write an extension that uses contributes/statusBarItems . Make sure the doc is clear, that things work, and esp that you can elevate this static item into a dynamic item from source.

[jrieken]

• Create an extension guide
• Extensions samples repo
• Add a finalized API: npx vscode-dts main
• Add a proposed API:
  • First add the proposed API to the package.json (see below)
  • Then run npx vscode-dts dev to get the typings

	"enabledApiProposals": [
		"quickPickSeparators"
	],

Note the name of the proposed API is gathered from the file name in the vscode-dts folder

[gjsjohnmurray]

	"enabledApiProposals": [
		"quickPickSeparators"
	],
    

In this case, contribStatusBarItems I assume?

[bpasero]

Pretty 👍 , I noticed if you call vscode.window.createStatusBarItem with an existing item but set a different alignment and priority, the item would not move. But not a big deal I think, so I did not file an issue for that.

[jrieken]

different alignment and priority, the item would not move

I did that on purpose. The API marks them as readonly and I extended that restriction* into the static items. (*) IMO this is a good restriction because otherwise extension can make the status bar "flicker" a lot (move from far left to far right for instance)