UI - add console logging function

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49978

• Created at 2018-10-15 19:26:38 by mreynolds (@mreynolds389)
• Closed at 2018-10-23 16:29:03 as fixed
• Assigned to mreynolds (@mreynolds389)

---

Issue Description

We are logging, console.log(), all the CLI commands in the UI. To make sure the formatting is consistent we should create a simple logging function:

log_cmd(js_function_name, cmd_description_text, cmd_array);

log_cmd("load_repl_config", "Load all the replication data into the UI forms", cmd);

Console output:

CMD: load_repl_config - Load all the replication data into the UI forms: dsconf -j ldapi://%2fvar%2frun%2fslapd-localhost.socket replication get --suffix=dc=example,dc=com

[389-ds-bot]

Comment from mhonek (@kenoh) at 2018-10-16 10:54:37

Good idea. Additionally, however, I believe the logging itself should be turned off by default in production, and only turned on when the user explicitly asks for it, maybe some hidden checkbox. And, the call itself should be guarded for existence as the console.log() may not be present in some browsers, hence it has potential to generate a lot of errors in the console itself.

[389-ds-bot]

Comment from mhonek (@kenoh) at 2018-10-16 10:54:38

Metadata Update from @kenoh:

• Custom field component adjusted to None
• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2018-10-17 01:01:42

@kenoh Flip side is that console logging is cheap on the client, and will make error report submissions simpler. I think logging by default is fine for this application,

However, console.log not being universal ... is that true? I would hope we could find a way to standardise or detect what logging we need inside the log_cmd.

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-18 00:02:25

#3041

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-18 00:02:27

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to review (was: None)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-10-23 16:29:05

Metadata Update from @mreynolds389:

• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)