-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
doc: update trace_event doc in tracing.md #20092
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
|
@nodejs/documentation @nodejs/diagnostics |
This comment has been minimized.
This comment has been minimized.
vsemozhetbyt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the effort to make docs better!
I've left some comments about format nits)
doc/api/tracing.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In docs, lines are usually wrapped within 80 characters, otherwise, there will be doc linting issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vsemozhetbyt, 🙏 for your advise. Learned make lint script and and updated according to linting.
doc/api/tracing.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If not in code fragment, the uppercased variant is preferred: [V8]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vsemozhetbyt, after learning make lint script, updated to the uppercased variant, ✌️
doc/api/tracing.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is -> Is for consistency with other items?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would just go with "An empty placeholder." maybe or something. Unless we have some rule about needing complete sentences...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@apapirovski & @vsemozhetbyt, 👍& 🙏for both of your suggestions. Updated to go with "An empty placeholder.", as it seems "short and sweet" for now. Happy to do follow-up PR, if there's a new content for node.
doc/api/tracing.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trace Event -> Trace Events?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, events are plurals. Updated. 😅👶
doc/api/tracing.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As .md files are only sources for .html documents in https://nodejs.org/api/, links usually refer to HTML docs. Also, ASCII sorting in bottom references is preferred. So this fragment may be written in such way:
[Performance API]: perf_hooks.html
[V8]: v8.html
[async_hooks]: async_hooks.htmlThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vsemozhetbyt, learned the documentation scripts (i.e. make doc) & the built .html files' relationship to the docs, the interesting ASCII sorting preferences. Will keep that in mind going forward. 🙏for this piece of valuable review comment.
|
@vsemozhetbyt, really appreciate your time in the previous comments about format nits. I've updated, and tried my best to reply the each outdated comment accordingly, to "kind of" recap the educational takeaway from the review comments. 👨🎓Please have another quick review, when you have time. 👍 P.S.: I'm actually a mentee in the mentorship, awaiting to be paired with a mentor. So I just wanted to find a "good first time" labelled issue to try to contribute a "small" update, and learn the node.js ecosystem before the mentorship kicks in full gear. So really appreciate your patience about the format nits. 🙏 |
vsemozhetbyt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doc format LGTM)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@vsemozhetbyt , confirmed that my local master did not have the sync with upstream master. Once the local branches are sync'ed with upstream, the PR looked ok. Can you try the CI-lite build again? Thanks. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Hi, thanks for re-running CI-lite: https://ci.nodejs.org/job/node-test-pull-request-lite/549/. Just a simple question to ensure I didn't get confused. Per previous note below, is there anything I can do to help make the CI-Lite passing and the lander successful? I'm happy to help out, if there's any thing I can do to help. Thank you!
|
|
@BeniCheni if you could rebase your branch to the upstream master, as shown here, that would help. |
|
@BeniCheni It seems the rebase process is rather complicated in this case. I have tried to do this cloning your branch. If it is OK, I can push the result back and we will see if everything is OK. If something goes awry, you can just create a new PR with the same changes. |
|
|
|
@BeniCheni I think you might have @-tagged the wrong person |
|
Corrected the previously wrong @ -tagged person. |
|
@BeniCheni I've squashed all the commits in one and force-pushed in your branch. It seems everything is OK, but please, check if the changes are identical to yours intended, If they are, we may need another positive review for this and then land as is. |
|
@trivikr Please, take a look if this is still good for you. |
|
@vsemozhetbyt, I’ll reviewed and confirmed the changes are identical to mine intended. |
|
CI-lite is green 🎉, so let us wait for one more positive review and then land) |
|
@vsemozhetbyt Looks good! 👍 |
|
Landed in 8b012e1 |
Change title from
tracingtotrace_eventin the documentation content. Update the description ofnode,node.async_hooksandv8category to contain information highlighted in #16315.Fixes: #16315
Checklist
P.S.: After reading #16315, the the async_hooks and v8 documentations in details, I'm hoping to give this "good first issue" issue an attempt.
Thanks for your time to review in advance. Hoping the PR looks okay. Happy to update according to any review feedback. ✌️