Skip to content

Comments

chore: remove console.log statements from production code#102

Closed
Kunal1522 wants to merge 1 commit intom-lab:mainfrom
Kunal1522:fix/remove-console-logs
Closed

chore: remove console.log statements from production code#102
Kunal1522 wants to merge 1 commit intom-lab:mainfrom
Kunal1522:fix/remove-console-logs

Conversation

@Kunal1522
Copy link
Contributor

Problem

Three console.log calls were left in measure.js from development:

  • Logs NDT server machine and location on every test start
  • Dumps the full NDT downloadComplete data object to the console
  • Logs MSAK server machine name on download start

These expose internal data structures to any user who opens browser DevTools.

Fix

Removed all three console.log calls from measure.js.

Three console.log calls were left in measure.js from development:
- Logs server machine and location on every NDT test start
- Logs the full NDT downloadComplete data object
- Logs MSAK server machine name on download start

These expose internal data structures to any user who opens browser
DevTools and add noise to the console in production.
@robertodauria
Copy link
Contributor

Same reasoning as with #101 - this is mostly intentional, and valuable debug information when something does not work.

Nothing about server name and location is supposed to be private, anyway. In fact, we encourage looking at the JS console in case of issues, and knowing the exact server has been helpful in the past.

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