Failed to load lookup field source list in modern list view edit column pane when the lookup field "LookupList" property is lowercase

[yungfu]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

No response

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

No response

Describe the bug / error

Create a lookup field by pnpjs sp.web.lists.getById().addLookup, the lookup field is added successfully, and it can be edit in classic experience field setting page. But when you try to edit field from modern list view header Column Setting -> Edit command item, the *Select a list as source in opened right pane is always the first one, not the correct value.
If you try to add a lookup field with schema xml, when the LookupList attribute is lowercase, this issue disappeared, but if the property is uppercase, this issue can be reproduced. I think this is caused by the uppercase LookupList property.

Steps to reproduce

1. Create a lookup field by schema with uppercase LookupList property
2. Edit created field in classic experience field edit page, the source list is correct
3. Edit created field in modern list view page right pane, by click Field Setting -> Edit command in list view header, the source list property is incorrect
4. Create a lookup field by schema xml with lowercase LookupList property, this issue disappeared.

Expected behavior

Created lookup field can display the correct source list in modern list view page column edit pane no matter the LookupList property is lowercase or uppercase.

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.