feat(node): allow and recommend to provide a specific root

[skjnldsv]

This should ensure we are working from a specific point
This makes sense for most dav ressources

const file = new File({
	source: 'https://cloud.domain.com/remote.php/dav/files/emma/Photos/Berlin/picture.jpg',
	mime: 'image/jpeg',
	owner: 'emma',
	root: '/files/emma',
})

file.basename: 'picture.jpg'
file.extension: '.jpg'
file.dirname: '/Photos/Berlin'
file.path: '/Photos/Berlin/picture.jpg'
file.root: '/files/emma'
file.isDavRessource: true

[codecov]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (364866c) compared to base (e953b2a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #574   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          160       170   +10     
  Branches        45        50    +5     
=========================================
+ Hits           160       170   +10     

Impacted Files	Coverage Δ
lib/files/node.ts	100.00% <100.00%> (ø)
lib/files/nodeData.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[ChristophWurst]

What will the root be used for?

[skjnldsv]

What will the root be used for?

Specifying the workdir for example.
It allow to scope the files you're working with to a specific service.

Like currently, if I get files from webdav and process them into File or Folder, I have no way of knowing their relative path (from the root).
Like in the files app, we use /Photos/Berlin/picture.jpg type of paths, not /files/emma/Photos/Berlin/picture.jpg

I could put them into the attributes, but I think it's cleaner as an official implementation.

[ChristophWurst]

If you take the source, remove basename and dirname you already get the root, don't you? It sounds like there will be two approaches to achieve the same goal. Either you spec basename and dirname or source and root?

[skjnldsv]

If you take the source, remove basename and dirname you already get the root, don't you? It sounds like there will be two approaches to achieve the same goal. Either you spec basename and dirname or source and root?

Well, you don't know the root
See the difference between files and trashbin:

• https://domain.com/remote.php/dav/trashbin/admin/trash/100.txt.d1674135367
• https://domain.com/remote.php/dav/files/admin/100.txt

Here the roots are respectively:

• /trashbin/admin/trash
• /files/admin

And we cannot detect this, so we have to manually be able to provide that information