Open hanzei opened 3 years ago
So the meeting-id passed in as argument will get updated here
as jitsiNameSchemeAsk is not a case here.
do you think a new case should be added to it???
That switch
only takes care what meeting topic to use. I think my comment here should guide you into the right direction.
Okay now this confuses me, the RootId is passed as empty string for both the cases and the code executes the same line/request for both the cases then what causes the problem here??
https://github.com/mattermost/mattermost-plugin-jitsi/blob/14107b6a514180ca0867761c0cba72bcc77518ac/server/api.go#L232 is the line that get executed when a meeting is started after a naming schema was requested. Right now it simply uses an empty rootID. You need to store the rootID into the request context(https://github.com/mattermost/mattermost-plugin-jitsi/blob/d533d34c9b376b3b273b452f44d0fefeae46a7fd/server/api.go#L32) and then access it here.
hey @hanzei this is only pending for merge.
While testing https://github.com/mattermost/mattermost-plugin-jitsi/pull/158, I found one uncovered edge case: If the naming schema is set to
ask
, the ephemeral message generated when typing/jitsi start
is correct posted in the RHS, but the following meeting isn't.