Forgotten 'console.log' in the code

[bryandidur]

I'm Submitting a ...

[x] Bug report
[ ] Feature request
[ ] Support request

Steps to Reproduce

1. Clicking on the datetime input logs a "CLICKING 2!" message in the console.

Expected Results

No debug logs.

Actual Results

Logs a "CLICKING 2!" message in the developer console.

Minimal Reproduction of the Problem

See this sandbox to inspect the debug message https://codesandbox.io/s/lively-worker-vsqu1?file=/src/App.js

Other Information (e.g. stacktraces, related issues, suggestions how to fix)

None

[SachaG]

Glad I'm not the only one who sometimes forgets console.logs in production code!

[Ashirogi-Muto]

I just checked out the file DateTime.js, the source of the log and I didn't find the log statement! Am I doing something wrong?

[bryandidur]

I don't know. But the log exists, as you can see in the sandbox.

[Ashirogi-Muto]

I am using this library in my company's product which is built in React and yes I can see the log there too!

[ali-wells]

It seems to be in the minified version sitting in the dist directory, I think it needs re-building from the current source as DateTime.js doesn't have that line now

[johnhunter]

Should probably add eslint rule https://eslint.org/docs/rules/no-console

[NoPhaseNoKill]

Do we have an ETA on when this will be fixed?