🐞SPFx - Update serve.json's schema to include serveConfigurations for IntelliSense

[andrewconnell]

Target SharePoint environment

other (enter in the "Additional environment details" area below)

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

macOS

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

All SPFx projects, but mostly an issue with SPFx extensions

Describe the bug / error

The schema for ./config/serve.json, https://developer.microsoft.com/json-schemas/core-build/serve.schema.json, is missing the section serveConfigurations.

This means developers won't get IntelliSense with included docs when editing this file. Can be resolved by fixed by updating the schema to include & doc up all the options for serveConfigurations.

Steps to reproduce

1. Create new project
2. Use any type of component when prompted
3. Open said project in VSCode
4. Open ./config/serve.json
5. Move mouse over serveConfigurations property and observe tooltip warning "Property serveConfigurations is not allowed"
6. Developer curses at VSCode and 😭 in solitude... kittens rush for safety to avoid being kicked by said developer

Expected behavior

1. Create new project
2. Use any type of component when prompted
3. Open said project in VSCode
4. Open ./config/serve.json
5. Observe IntelliSense when modifying values under the included serveConfigurations
6. The Microsoft engineer who took the time to update this file, on their way home from work to enjoy a good streaming movie, when picking up their take-out tacos 🌮, comes to find out someone paid it forward as thanks and now they enjoy free 🌮 for their contribution to developers across the globe.

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[AJIXuMuK]

Thanks @andrewconnell - this will be fixed in the next release

[AJIXuMuK]

1.15.2 is out - this should be fixed

[ghost]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues