From 7924f0ea7320dc2b728752682e243a3ad61dec80 Mon Sep 17 00:00:00 2001 From: Alain Bourgeois Date: Tue, 8 Dec 2020 15:33:09 +0100 Subject: [PATCH] Exclude port from chatContainerStr The port has no meaning in this context and will allow compatibility with Windows where colon are forbidden in file/folder names. It has not impact on `solidcommunity.net` nor `inrupt.net`, or any of podProvider that do not use a specific port. see issue https://github.com/solid/solid-panes/issues/262 --- src/create.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/create.ts b/src/create.ts index 8a6cb0b..30b0153 100644 --- a/src/create.ts +++ b/src/create.ts @@ -43,7 +43,7 @@ ${ns.rdf('seeAlso')} <${chatThing.value}> . function determineChatContainer (invitee, podRoot) { // Create chat // See https://gitter.im/solid/chat-app?at=5f3c800f855be416a23ae74a - const chatContainerStr = new URL(`IndividualChats/${new URL(invitee.value).host}/`, podRoot.value).toString() + const chatContainerStr = new URL(`IndividualChats/${new URL(invitee.value).hostname}/`, podRoot.value).toString() return new NamedNode(chatContainerStr) }