microsoft / microsoft/Microsoft-Fabric-workload-development-sample
Validating fabric item name change
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 58
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Workload Manifest Schema Version (if relevant)
No response
Your Question
Users of our workload may rename assets using the settings ui. Because of the way we process our assets, we need to validate the name that the user enters. For example, we do not allow names to begin with a number. When we get the update request and the name is invalid, we are returning a statusCode of 400 (bad Request). I have also tried to return 406 (unacceptable). In either case, the Fabric UI continues to show the invalid name.
How can we reject the name change and have the UI revert? Is there a way to validate the name change in the client?
Context / Background
No response
Additional References
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the settings UI name-change flow and the update request handling described in the issue; no files or tests are named. Determine how invalid names are reported to the client and what response causes the UI to revert, then verify that an invalid rename is rejected and no longer displayed.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100