Test Getting Started Extension Point

[JacksonKearl]

Testing #116414

• anyOS @rebornix
• anyOS @stevencl

Complexity: 3

Create Issue

---

This iteration we added a new (proposed api) contribution point for getting started items, test that it makes sense to use and works as expected.

1. New extension with proposed API,
2. In package.json contributes clause, add a gettingStarted field.
3. Verify that intellisense guides you through creating items for the getting started content
4. Verify that when running the extension, you see the contributed items in the Help: Getting Started page and can work through them

[stevencl]

This all worked, although there was no auto complete for adding the gettingStarted field itself (I got intellisense for the items within the gettingStarted field though).

[JacksonKearl]

Thanks! No autocomplete for the gettingStarted field is expected as it's still proposed. Hovering over the filed once written should give information though.

[rebornix]

It works in overall but I'm not sure how one extension will clear the get started states other than changing the command ids used in the steps.