Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[main > release/client/2.3]: Handle Location redirection for getSharingInformation call (#22551) #22619

Merged
merged 2 commits into from
Sep 25, 2024

Conversation

jatgarg
Copy link
Contributor

@jatgarg jatgarg commented Sep 24, 2024

Description

Main PR Link: #22551

AB#15188

Handle location redirection when calling getSharingInformation in ODSP Driver. Since this call does not include the v2.0 which calls the API without the drive and item ID, these calls fail if the tenant has been renamed. Sometimes this creates issues when creating a new page, since the user could not get the sharing link to the new page. GetFileItem call also returns the new siteUrl to which the file has been moved. Use that to detect the new domain and then change the resolved url accordingly.

…#22551)

## Description


[AB#15188](https://dev.azure.com/fluidframework/internal/_workitems/edit/15188)

Handle location redirection when calling getSharingInformation in ODSP
Driver. Since this call does not include the v2.0 which calls the API
without the drive and item ID, these calls fail if the tenant has been
renamed. Sometimes this creates issues when creating a new page, since
the user could not get the sharing link to the new page.
GetFileItem call also returns the new siteUrl to which the file has been
moved. Use that to detect the new domain and then change the resolved
url accordingly.

Co-authored-by: Jatin Garg <[email protected]>
@jatgarg jatgarg self-assigned this Sep 24, 2024
@github-actions github-actions bot added area: driver Driver related issues area: odsp-driver base: release PRs targeted against a release branch labels Sep 24, 2024
Copy link
Contributor

Warning

WARNING: This PR is targeting a release branch!

All changes must first be merged into main and then backported to the target release branch.
Please include a link to the main PR in the description of this PR.

Changes to release branches require approval from the Patch Triage group before merging.
You should have already discussed this change with them so they know to expect it.

For more details, see our internal documentation for the patch policy and processes for
patch releases.

@msfluid-bot
Copy link
Collaborator

msfluid-bot commented Sep 25, 2024

@fluid-example/bundle-size-tests: +245 Bytes
Metric NameBaseline SizeCompare SizeSize Diff
aqueduct.js 460.88 KB 460.92 KB +35 Bytes
azureClient.js 559.03 KB 559.08 KB +49 Bytes
connectionState.js 680 Bytes 680 Bytes No change
containerRuntime.js 261.68 KB 261.69 KB +14 Bytes
fluidFramework.js 401.54 KB 401.56 KB +14 Bytes
loader.js 134.17 KB 134.19 KB +14 Bytes
map.js 42.43 KB 42.44 KB +7 Bytes
matrix.js 146.59 KB 146.6 KB +7 Bytes
odspClient.js 526.18 KB 526.23 KB +49 Bytes
odspDriver.js 97.8 KB 97.82 KB +21 Bytes
odspPrefetchSnapshot.js 42.76 KB 42.78 KB +14 Bytes
sharedString.js 163.27 KB 163.28 KB +7 Bytes
sharedTree.js 392.01 KB 392.02 KB +7 Bytes
Total Size 3.3 MB 3.3 MB +245 Bytes

Baseline commit: 6b9f122

Generated by 🚫 dangerJS against d68b000

Copy link
Contributor

@AndreiZe AndreiZe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@frankmueller-msft frankmueller-msft enabled auto-merge (squash) September 25, 2024 20:54
@jatgarg jatgarg enabled auto-merge (squash) September 25, 2024 20:55
@jatgarg jatgarg merged commit c1311b2 into microsoft:release/client/2.3 Sep 25, 2024
31 checks passed
@jatgarg jatgarg deleted the rc23 branch September 26, 2024 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: driver Driver related issues area: odsp-driver base: release PRs targeted against a release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants