SharePoint
Feedback by UserVoice

Pat Miller (MSFT)

My feedback

  1. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Rather than a new extension type, I think of these as improvements to the existing field customizer. You can extend the sort/filter logic, and so forth. I guess I view it all as "I added a field to the list. I need to display the content, I need to edit the field, I need to display the column header, I need to sort and filter the column.

    But Yes - I think it makes sense.

  2. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Ah, interesting. I'll see what is possible here. The onDispose should work, so let's just call that one a bug. I'll follow up with folks and see if we are missing calling out to it. Modiyfing the command sets during execution isn't something that has come up in discussions, but I can see the usefulness of it. Maybe it will be straight forward.

    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Hey Alex, the first two things exist today, at least as far as the built in experiences are concerned (buttons / commands don't have a notion of a "pressed" state). To change the title, you would add code like:

    @override
    public onRefreshCommand(event: IListViewCommandSetRefreshEventParameters): void {

    if (event.commandId == "COMMAND_1") {
    event.title = "Showing You!";
    event.visible = true;
    }
    }

    onDispose currently exists on the base extension class. Just add the following to your code:
    @override
    public onDispose()
    {

    }

  3. 102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Just a few clarifying questions.
    1 - Do you require offline / airplane mode, or is it ok for extensions to require a "connected" environment?
    2 - Do you want to use the workbench itself as the test bed, or would it be better (or at least sufficient) for the workbench to have a series of pickers (what list and what field do you want to test on?) and a then it kicks off a request with the correct debug strings, etc?

    Webparts 'tend' to stand on their own to some extent, but extensions seem to require more connection to the underlying app IMHO. I completely agree that we need to improve the dev cycle for GA - I just want to make sure we spend the resources in the right place.

  4. 78 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →

    We’re reviewing your suggestion. Like Pat already noted in the comments, we are looking into this one and hopefully can make this happen relatively soon. Thanks for your feedback!

    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Hmn. Maybe I need to step back one step. I guess there are 4 different possible places to get involved.

    1 - In yeoman
    2 - During a build
    3 - during package upload/activation
    4 - during code execution

    Those are probably in order of complexity as well :)

    Which area would you like to drill into?

    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    We were discussing this yesterday. There are a couple of things to consider, and getting some feedback would be good.
    1 - There are times when there is something new at a top level (like the new extensions, or a new type of extension). One possibility here is that in Yeoman, there is a top level choice "Add Preview (not supported) component".
    2 - There are times when you are using supported components (say a WebPart), but you are using a beta API (say the GraphHttpClient). What would be a good approach here? Intellisense saying "Beta" at the beginning of the description? A warning message each time you use a beta API? ( don't know what is even possible here to be honest)

  5. 420 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Pat Miller (MSFT) commented  · 

    Hey AC - While I know what you mean here, can you refine this to target the modern experiences? For example, PlaceholderMain is an asp.net masterpage div that doesn't exist in the newer code. Would you think of Pre/Post Placeholdermain to be ContentHeader and ContentFooter (as opposed to PageHeader and PageFooter?

    Additionally, how would you expect scrolling to work in this scenario? For example - what should happen with a listview with infinite scroll vs. a page with 500k of text?

Feedback and Knowledge Base