Find out intended behaviour to shortNameForFolder

[michielbdejong]

shortNameForFolder returns 'example.com' for 'https://example.com/' and '/' for 'https://'. I'm not certain this is actually by design, it might be that the intended behaviour was that the domain root would already get labeled '/'. That would make more sense to me for a filebrowser.

[michielbdejong]

See https://github.com/solid/solid-ui/blob/master/test/unit/acl/acl-control.test.ts#L44-L65 (edited) for the current behaviour.

[SharonStrats]

I'm thinking things may have gotten moved around, the link above gives a 404 error.

[michielbdejong]

Edited the link, thanks.

[megoth]

You might want to double check this with @timbl if you're still uncertain about the intended behavior.

[michielbdejong]

@timbl do you know?