-
Notifications
You must be signed in to change notification settings - Fork 3k
events: Added note about immediate firing of periodic events #6274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The Event class has no documentation :) But it's an very good note I think, alerts the reader that something's up and if they're sufficiently motivated, they can check on it themselves. |
Oh wow, there really isn't... There is doxygen in the codebase, but for some reason it isn't generated. Will have to look into this: @AnotherButler, just fyi |
Also @AnotherButler quick question, when is doxygen updated on the developer site? Is it every minor release? |
That's strange, it looks like all the comments were stripped out of the file? The Event.h file hasn't been touched in a long time (9 months)... |
@adbridge Thoughts to above? |
/morph build |
The last PR that touched the header file: #4434 |
On second glance, what's currently in the mbed repo looks fine. Wondering if the doc generation isn't capturing this/these files. |
Build : SUCCESSBuild number : 1363 Triggering tests/morph test |
Exporter Build : FAILUREBuild number : 1015 |
Not restarting CI quite yet. @studavekar What do you take of the export failure? |
I am not sure, at least the failure look legit but in no way related to this change.
|
Alright, gonna see if this goes 2/2. |
Exporter Build : SUCCESSBuild number : 1018 |
Description
Added note about immediate firing of periodic events
see #6256
cc @pauluap, @kjbracey-arm
Pull request type