We would like to be able to create an SPFx form and associate it with the List/Content type Disp, Edit, New form so that no matter how a user finds a list item (search, OOB list view, custom list view, etc) they see our custom form. Currently our only option is to create a completely disconnected experience in which we write a custom list view that points to custom form pages.

Alternatively support field customizers with edit model to enable custom field editing experience.

Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for QuickLaunch & PlaceholderMain

Cross-reference:
https://github.com/SharePoint/sp-dev-docs/issues/625

It would be great if we are able to use font icons instead of url to images for Command Set extensions buttons icons.
This allow 3d party extensions look more aligned with 1st party (same style, same icon color)

The LivePersonaCard control, which renders a user's full profile card, can be loaded in a SPFx solution with LoadByComponentId. However, it is unclear whether this will be supported in the future.

The PnP reusable controls has a Pull Request to provide developers with a LivePersonaCard control, but it is currently in holding pattern until it can be confirmed that LivePersonaCard (and LoadByComponentId) will be supported.

Please empower 3rd party developers to build rich user-aware SharePoint solutions by providing solution for the live persona card.

Cross-reference: https://github.com/SharePoint/sp-dev-fx-controls-react/pull/353

SharePoint modern pages Social bar View count apparently does not use Search Managed property ViewLifeTime or ViewsLifeTimeUniqueUsers. Fiddler traces shows that some Internal Apis are used to fetch modern pages social bar view count. It would great if Microsoft release Public documented API so that custom SPFx web parts/extension in need of modern page view count, could utilize the API

Please provide a well-known placeholder for the property pane or better a similar placeholder that let us create a sidebar.

Having this ability would let us create powerful sidebars/toolbox extensions. This would be a super cool enhancement!

Actually, the only way to paginate list items using the new REST APIs is to use __next property. There's no way to have a full working pagination using $top and $skip token as for any other REST call.
See my comment here:
http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72.aspx

There's an undocumented API (https://tenant.sharepoint.com/vtibin/homeapi.ashx/ ) to follow sites and query data around those concepts. For corporate intranet scenarios, we often want to present the data a different way, surfacing native SharePoint capabilities. In order to add a "follow" button on an SPFX web part, we'd need an API to access that.

Related GitHub issue https://github.com/SharePoint/sp-dev-docs/issues/1689

Provide option to enable\disable event firing from Remote Event Receivers in SharePoint Online (CSOM/API) similar to SSOM - EventFiringEnabled

Provide a SharePoint Framework mechanism/API that allows for Site or Site Collection Read/Write of Key/Value pair properties for use in SPFx related configuration and customizations. Similar to how the property bag was used in classic.

One use case is for storing configurable properties or even user personalization configurations written and read by an SPFx solution.

This is one of many uses cases that would make this feature valuable, so in addition to your vote, please feel free to comment with additional ways in which this feature could provide additional value.

REST API should be fixed when getting single value Managed Metadata since it returns the Id instead of the actual value, which then requires another call to get the value. Without this you cannot show a list of items/docs with the single Managed Metadata value. Note that "Allow Multiple" Managed Metadata works fine as it returns a collection of actual values.

For details see: http://sharepointificate.blogspot.com/2014/05/taxonomy-columns-sharepoint-2013-list.html

The Web class in the CSOM lacks the ability to send a web to the recycle bin. Currently it's only possible to delete a web by using Web.DeleteObject() which makes restoring from recycle bin impossible.

Please consider adding a Recycle() method to the Web class.

Add support for adding CSS and Javascript on Sharepoint Modern Pages.

Here is an example implementation on github, but certainly my organisation will not implement it (straight out of github project), unless Microsoft can push this capability to Sharepoint:
https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor

Please see this image for more details, where I am trying to suggest adding a new Web Part for Scripts+CSS:
https://i.imgur.com/dtpIzdY.png

This capability is available in old Sharepoint Pages, so hopefully it should be easy to push in Modern Pages (which I really like to use).

Regards

There is currently no good way to do enterprise level automated deployments of an SPFX addin into a SharePoint 2016 on Premise environment..

Consider a case where there are 1000 site collections and we would need to deploy an SPFX app to all sites automatically. Currently there is no way to perform this deployment in an automated fashion. It is not possible through powershell, csom, c# or in an administrative UI.

Having this ability would solve a large hole in capabilities with SharePoint Framework

Please consider adding support for setting/retrieving doucment set properties on a content type. We need to be able to set properties like Shared columns, Welcome page and Welcome page view on the document set.