Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not precisely something we’re planning to do right now. That refers more specifically on the vue.js usage. You can though use any JavaScript framework in SharePoint Framework implementation. We are looking to enable more flexibility on the list and library templating in future though.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. Using C# based customizations in SharePoint Online in safe way was possible in isolated scenarios with Sandbox solutions, but this capability has been removed. SharePoint hosted apps are hosted in the SharePoint and there’s no way to provide code level isolation which would be required for these scenarios.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. We do understand the value of SP Designer in older scenarios but are not planning to currently invest in the modernization of it for the SharePoint 2016 or SharePoint Online.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now through SP dev team. This falls more on the Windows server side enhancements and our team cannot, unfortunately, act on this as such. We do though appreciate your input and agree that TMG was a great product for a purpose in on-premise.

This is absolutely supported and you can have as many extensions or web parts in single solution talking between each other. There are numerous options for the components to communicate with each other. One of such options is demonstrated in following sample in SharePoint GitHub – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rxjs-event-emitter. Since this is not really a new feature request, we will close the issue. Would suggest having questions and discussions in StackExchange, GitHub or in SP Tech Community.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now

Thx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.

Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, we need to have more specific requests around what’s needed. We would appreciate more specific properties which you need so that we can evaluate exposure of them one-by-one. Thx.

Thank you for your input around the SharePoint PnP PowerShell. PnP CommandSets are however not part of the official product, so we support and have a discussion around them in the GitHub. In this case, would suggest creating a new entry to the issue list in the PnP-PowerShell repository at https://github.com/SharePoint/pnp-powershell/issues with these details. Asks are understandable and absolutely reasonable. Do also remember that PnP effort is dependent on the community contributions, so we cannot guarantee on the timelines for addressing any requests.

Thx for your suggestion and time taken for providing us your input.

No idea what’s being asked here, so closing. Thx for your submission, but we can’t help with this.

Closing due inadequate details on the request.