selectedRows is null on initial run of _onListViewStateChanged

[Tanddant]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

Windows

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

• Edge Version 132.0.2957.140
• SPFx version 1.20.0
• Node.js version 18.17.1
• "New modern", "Post modern", "New new" - or whatever you want to call the new list layout

Describe the bug / error

I'm building a List View Command Set extension

When the page is loaded my, and my _onListViewStateChanged(....) function is run for the first time, the this.context.listView.selefctedRows is undefined, rather than an empty array, this change seemingly happened over night.

Steps to reproduce

Once you create a new List View Command Set extension the _onListViewStateChanged is added automatically, flip the logic as such: compareOneCommand.visible = this.context.listView.selectedRows.length === 0 and you should observe the behaviour

Expected behavior

this.context.listView.selectedRows should be an empty array if no rows are selected, even upon the first run.

[Ashlesha-MSFT]

Hello @Tanddant,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@Tanddant ,
We were able to reproduce the issue. The problem arises because this.context.listView.selectedRows is undefined, as the state has not been established yet. This essentially means there is no selection to track at the moment.

[Tanddant]

@Ashlesha-MSFT, I understand why it happens, but this is a changed behavior, from in the past, which breaks existing solutions 😊

[Ashlesha-MSFT]

@Tanddant,
I understand why this issue is occurring, but I agree that this change in behavior is breaking existing solutions. We will log this as a bug, and our engineering team will look into it.
Thank you for your patience!

[Tanddant]

@Ashlesha-MSFT Thank you, highly appreciate the extra effort you guys have started putting into the sp-dev-docs - good job 💪