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

Client: add silent property #20

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Client: add silent property #20

wants to merge 1 commit into from

Conversation

peaBerberian
Copy link
Collaborator

We had a request from some external (not Canal+) partners to not output player logs while they were debugging issues because they were too verbose and their debugger didn't perform well.

Considering that the main scenario where we want to output the most logs on our side are when debugging issues, this is not something we want in cases like here where we're both testing the same application.

I propose this solution instead: When importing dynamically (at application runtime) the client script, a caller might set a supplementary silent: true option, which will allow to still send the log to the RxPaired-server, yet will not output the log in the usual console.

That way, people debugging on regular browser debuggers will not be bothered by logs, yet we'll still be able to see them through RxPaired.

@peaBerberian peaBerberian added server Update RxPaired's Server part client Update RxPaired's client part and removed server Update RxPaired's Server part labels Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Update RxPaired's client part
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant