In Blazor File Manager component, the rename operation is not working when ShowFileExtension property enabled.
Root cause
The reported issue occurs due to the incorrect path update and the code in the Azure file provider.
Solution description
Corrected the Azure controller and provider files to overcome the issue.
Reason for not identifying earlier
[ ] Guidelines not followed. If yes, provide which guideline is not followed.
[ ] Guidelines not given. If yes, provide which/who need to address.
Tag label update-guideline-coreteam or update-guideline-productteam.
[x] If any other reason, provide the details here.
Areas tested against this fix
Provide details about the areas or combinations that have been tested against this code changes.
[ ] Tested against feature matrix.
[x] NA
Is it a breaking issue?
[ ] Yes, Tag breaking-issue.
[x] NO
If yes, provide the breaking commit details / MR here.
Action taken
What action did you take to avoid this in future?
Feature matrix document updated
[ ] Yes
[ ] NO
[x] NA
Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.
[ ] BUnit, share corresponding MR.
[ ] E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.
If the same issue is reproduced in ej2, what will you do?
[ ] Resolved. Provide MR link.
[ ] NO. Created task to track it. Share task link.
[ ] NA
Is this common issue need to be addressed in the same component or on other components in our platform?
[ ] Yes
[x] No
Output screenshots
Post the output screenshots if an UI is affected or added due to this bug.
Blazor Checklist
Confirm whether this feature is ensured in both Blazor Server and WASM
[x] NA
[ ] Yes
[ ] NO
Is there any new API or existing API name change?
[ ] Yes. If yes, Provide API Review task link.
[x] NO
Is there any existing behavior change due to this code change?
[x] Yes. Add breaking-change label.
[ ] NO
Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)
[ ] Yes
[x] NO
Reviewer Checklist
[ ] All provided information are reviewed and ensured.
Bug description
Root cause
Solution description
Reason for not identifying earlier
[ ] Guidelines not followed. If yes, provide which guideline is not followed.
[ ] Guidelines not given. If yes, provide which/who need to address. Tag label
update-guideline-coreteamorupdate-guideline-productteam.[x] If any other reason, provide the details here.
Areas tested against this fix
Provide details about the areas or combinations that have been tested against this code changes.
Is it a breaking issue?
breaking-issue.[x] NO
If yes, provide the breaking commit details / MR here.
Action taken
What action did you take to avoid this in future?
Feature matrix document updated
Automation details - Mark
Is Automatedfield as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.If the same issue is reproduced in ej2, what will you do?
[ ] NA
Is this common issue need to be addressed in the same component or on other components in our platform?
Output screenshots
Post the output screenshots if an UI is affected or added due to this bug.
Blazor Checklist
Confirm whether this feature is ensured in both Blazor Server and WASM
Is there any new API or existing API name change?
Is there any existing behavior change due to this code change?
breaking-changelabel.Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)
Reviewer Checklist