List items that have an Audience field attached should be audience filtered when retrieved via the REST API.

For example, a list that has link items with the Audience field attached to target particular items at particular groups of people. If the REST APIs are used to retrieve items from this list, then the identity of the requesting user should be optionally used to filter the results based on audience.

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.

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.

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

I want to truncate the string which crosses the width and add '...' at the end. Currently I am able to do that except for adding the '...'. It can be done if the column formatter supports 'text-overflow: ellipsis'.

Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.

The idea is to have full control on user interaction with components.

In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...

Ideally to have access to domElement and data model of component.

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

Today, application extensions in SPFx (command sets, application customizers & field customizers) can't be tested within either the local or SharePoint Online hosted workbench. This is a bummer and a big step backwards to such a cool aspect to the development story with SPFx.

I get that you need a list to work with, but at a minimum, the workbench could have a static list with static data and no other functionality for us to test the customizations on.

My wish is that Microsoft adds support to the workbench for extensions before GA.

Allow REST clients to update list items a la SystemUpdate. That is, REST clients should be able to update list item metadata without creating a new version and without affecting system columns like authors and timestamps. The same idea for CSOM was recently implemented and I'm puzzled why the REST API is always left behind.
The CSOM idea:
https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/15147093-enable-listitem-systemupdate-via-csom

Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.

[Quote]
SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
[/Quote]

The Exception is also not pointing in the right direction.
1) It should be possible to create Site Collections providing the LCID
2) When an Invalid Lcid is passed, the exception should point in the right direction.

Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.

When creating sites using a site design (recipe), one of the available verbs is calling an HTTP-triggered Flow to perform some additional configuration on the newly created site.

When installing SPFx solutions in a site, we should similarly be able to specify an HTTP-triggered Flow to be called as a part of the installation process. This would not only allow developers to provision configuration beyond what's currently supported with Feature XML, but also create a consistent development experience across the different workloads (site designs vs. SPFx).

Observed behavior

When using a monorepo manager, like for example @microsoft/rush, the rush build command bundles all projects which are referenced in the monorepo - including SPFx projects.
When running gulp serve in (one of) the SPFx project(s), the bundle gulp command rebuilds the project. This is an unnecessary step, which would be nice if we could disable.

Proposed solution

Add a --nobuild flag support to the gulp serve command so we can start the local web server without rebuilding the SPFx code.

Simply hide the page canvas until all SpFx WebPart promises have resolved for modern sites

This would conceivably
1. Improve page load performance by not forcing the browser to display several loading gifs/fading animations at the same time
2. Improve user experience by displaying a complete page to the user rather than the page "jumping" constantly during the first 3-10 seconds of loading
3. Allow developers to add minor CSS updates to the page prior to render using the SharePoint Framework without noticeable "jumping"

The latest version of the SharePoint Framework Yeoman generator contains a mix of features that are GA and preview features (for example connecting to MS Graph, web part connections, extensions). Whether the generated solution can be run in production depends on the features used to build the web part. With that, when bundling the project, the toolchain should warn of any experimental features being used in the project which would prevent the solution from being deployed to production tenants. This would help developers avoid deploying solutions depending on experimental features to production tenants, only to see the deployment fail.

It is currently not possible to set the Owner of a SharePoint Group using REST API or maybe I don't have right syntax...