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

Do not check if room param is NaN in basic example server. #1231

Merged
merged 2 commits into from
Jun 1, 2018

Conversation

fantasy4z
Copy link
Contributor

isNaN('inputRoomName') returns true. Given a string of specific room name,
original implementation never assigns the specific room name to the
variable, resulting in generating new token of default room.

Remove the isNaN() call and simply check if the input value is truthy just
like what we do on other parameters.

Description

[] It needs and includes Unit Tests

Changes in Client or Server public APIs

[] It includes documentation for these changes in /doc.

isNaN('inputRoomName') returns true. Given a string of specific room name,
original implementation never assigns the specific room name to the
variable, resulting in generating new token of default room.

Remove the isNaN() call and simply check if the input value is truthy just
like what we do on other parameters.
Copy link
Contributor

@jcague jcague left a comment

Choose a reason for hiding this comment

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

LGTM, I agree there's no real need to keep checking this. Thanks!

@jcague jcague merged commit 696339e into lynckia:master Jun 1, 2018
zevarito pushed a commit to zevarito/licode that referenced this pull request Jul 4, 2018
Arri98 pushed a commit to Arri98/licode that referenced this pull request Apr 6, 2021
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.

2 participants