Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(JitsiConference): Separate conference name validation errors. #2466

Closed

Conversation

Romick2005
Copy link
Contributor

Separate thrown errors: "no conference name passed" and "it contains invalid characters like capital letters".

…ssed" and "it contains invalid characters like capital letters".
@jitsi-jenkins
Copy link

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

@@ -476,7 +481,7 @@ JitsiConference.prototype._init = function(options = {}) {
userName: config.statisticsDisplayName ? config.statisticsDisplayName : this.myUserId(),
confID: config.confID || `${this.connection.options.hosts.domain}/${this.options.name}`,
siteID: config.siteID,
roomName: this.options.name,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you changing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad that should be roomName. Initially I used roomName = options.name, but then I notice that it is mention as conference name in some places and room name on others so renamed all occurrence and this code was corrupted (

@saghul
Copy link
Member

saghul commented Feb 23, 2024

Since the errors are indistinguishable (no code or other attribute) why is this change useful?

Rollback invalid rename,
@Romick2005
Copy link
Contributor Author

So you can close it if it is not important.

@saghul saghul closed this Feb 23, 2024
@saghul
Copy link
Member

saghul commented Feb 23, 2024

Sorry, I don't think this PR improves the current code.

Thanks for taking the time to give it a try though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants