Skip to content

Conversation

@rejas
Copy link
Collaborator

@rejas rejas commented Mar 7, 2023

Fixes #3056

One question here would be if the default for this new option should be true or false.

True: keeps the current behaviour, nobody needs to change his config if they rely on this option

False: keeps the clock notifications quiet, doesnt waste time/resources, keeps the noise low

Maybe the original author @cybex-dev can weigh in on this, and why he added this notification.

@rejas rejas changed the base branch from master to develop March 7, 2023 21:03
@rejas rejas changed the title Add sendNotifications config option to clock module Add sendNotifications option to clock module Mar 7, 2023
@rejas rejas requested a review from khassel March 20, 2023 21:39
@khassel
Copy link
Collaborator

khassel commented Mar 20, 2023

@rejas will you wait for the reaction of the original author or shall I merge?

@codecov-commenter
Copy link

codecov-commenter commented Mar 20, 2023

Codecov Report

Merging #3059 (210296c) into develop (4ef030a) will increase coverage by 0.03%.
The diff coverage is 0.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@             Coverage Diff             @@
##           develop    #3059      +/-   ##
===========================================
+ Coverage    27.52%   27.55%   +0.03%     
===========================================
  Files           52       52              
  Lines        11568    11573       +5     
===========================================
+ Hits          3184     3189       +5     
  Misses        8384     8384              
Impacted Files Coverage Δ
modules/default/clock/clock.js 0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@rejas
Copy link
Collaborator Author

rejas commented Mar 20, 2023

@rejas will you wait for the reaction of the original author or shall I merge?

I'd like to know your opnion on my question regarding the default value first

@khassel
Copy link
Collaborator

khassel commented Mar 20, 2023

I'm fine with this, the other way round the majority of users would still have the unwanted noise.

May this should mentioned in the docs as a "breaking" change.

@KristjanESPERANTO
Copy link
Collaborator

I also think it makes sense to set the default to false.

@rejas
Copy link
Collaborator Author

rejas commented Mar 22, 2023

May this should mentioned in the docs as a "breaking" change.

In the CHANGELOG or where do you mean? The docs website doesnt have any version information.

@khassel
Copy link
Collaborator

khassel commented Mar 22, 2023

In the CHANGELOG or where do you mean? The docs website doesnt have any version information.

I meant the docs, the new property sendNotifications should be added there with a hint to the new default

@rejas
Copy link
Collaborator Author

rejas commented Mar 25, 2023

I meant the docs, the new property sendNotifications should be added there with a hint to the new default

Ok, will open a PR there "soonish". This PR is therefor ready to merge @khassel

@khassel khassel merged commit 6223584 into MagicMirrorOrg:develop Apr 1, 2023
@rejas rejas deleted the issue_3056 branch April 1, 2023 20:43
rejas added a commit to rejas/MagicMirror that referenced this pull request Apr 1, 2023
Fixes MagicMirrorOrg#3056 

One question here would be if the default for this new option should be
true or false.

True: keeps the current behaviour, nobody needs to change his config if
they rely on this option

False: keeps the clock notifications quiet, doesnt waste time/resources,
keeps the noise low

Maybe the original author @cybex-dev can weigh in on this, and why he
added this notification.

---------

Co-authored-by: veeck <michael@veeck.de>
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.

disabling CLOCK_SECOND notification

4 participants