nadment commented on PR #9533:
URL: https://github.com/apache/hop/pull/9533#issuecomment-6992268180

   Heads-up for the reviewers: commit dd80f3b6b7 changes the layout of the 
paths. The root now has two fixed folders that mirror the address of a site in 
SharePoint:
   
   ```
   <connection>:///sites/<site>/<library>/<folder>/<file>
   <connection>:///teams/<site>/<library>/<folder>/<file>
   ```
   
   For example `https://contoso.sharepoint.com/sites/Finance` is 
`m365:///sites/Finance`, and 
`https://contoso.sharepoint.com/teams/Communication` is 
`m365:///teams/Communication`. Before, the path started with the site name and 
the plugin looked for it under `/sites`, then `/teams`.
   
   Why:
   
   - A site under `/sites` and a site under `/teams` with the same name are now 
two different paths. A path can no longer switch from one to the other, and 
there is no precedence rule.
   - The root is always browsable, without any call to Graph. The sites are 
listed under `sites` and `teams` when the application is allowed to list them; 
with `Sites.Selected` the two folders are empty and the full path of a granted 
site still works.
   - A site is found with a single request, by its address, whatever the number 
of sites in the tenant.
   - The path is what follows the host in the browser, so it can be copied from 
there.
   - A `personal` folder for OneDrive could be added later without changing the 
existing paths.
   
   What it costs:
   
   - Every path has one more level. Paths written against the earlier commits 
of this PR need `sites/` or `teams/` after `:///`.
   - The root site of the tenant and subsites (`/sites/Finance/Audit`) are not 
reachable.
   - `teams` is the SharePoint managed path, not Microsoft Teams: the site of a 
team is under `/sites` on most tenants. The docs say so in the Teams channels 
section.
   
   The user manual pages, the unit tests and the description of #9531 are 
updated to the new layout.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to