[JITSI] Create an endpoint to generate a Jitsi URL

Open
#19,056 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, backend

Research direction

Start by locating the existing client-side Jitsi URL generation and the settings it checks. Then trace how clients obtain the roomId and how server endpoints are organized. Done means an endpoint accepts a roomId, returns the generated Jitsi URL, and the relevant clients can use it instead of generating the URL independently.

Written by the indexing model from the issue text.

Description

hacktoberfest
Description:

Sometimes we make changes on how the url for Jitsi calls is generated based on settings or something like this.
It should be better if instead of check all the settings and generate the url on each client side, we have an endpoint where we send a roomId and it returns a generated Jitsi URL.

Steps to reproduce:
Expected behavior:
Actual behavior:
Server Setup Information:
  • Version of Rocket.Chat Server:
  • Operating System:
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version:
  • Operating System:
Additional context
Relevant logs:
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/Rocket.Chat

All issues in RocketChat/Rocket.Chat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.