Closed Ryanclbryant closed 3 weeks ago
there are all kinds of places where there is no error checking
@rejas @sdetweil any objections to replace DOM_OBJECTS_CREATED
with MODULE_DOM_CREATED
?
DOM_OBJECTS_CREATED is send after all modules are done, MODULE_DOM_CREATED is send for each module, so how would you implement the logic in the updatenotification module then?
@rejas but in this case if we use MODULE_DOM_CREATED
, i'm not sure that Module.definitions
is set correctly
we have to check around this
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I've had a broken third party module for several months and didn't realize it; the update was available but because the issue was with creating the dom on initial load we had issues with receiving the required notifications.
I noticed that
MODULE_DOM_CREATED
is being sent, but neverDOM_OBJECTS_CREATED
, which updatenotification.js relies on here.Would it be a feasible replacement for updatenotification to look for the
MODULE_DOM_CREATED
notification instead?Sample of a successful load:
Sample of where one of any modules experiences an error during initial dom creation:
Making this change would support the module to raise the flag that updates are available, which actually resolved the error that MMM-Todoist was hitting.