Eliminate some unnecessary nesting in the reference docs #2899
+1
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ekzhang
approved these changes
Feb 25, 2025
mwaskom
added a commit
that referenced
this pull request
Feb 25, 2025
…)" This reverts commit d8fed17.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that we're pulling
FunctionCallup to the top-level namespace, we should also include it in the sidebar of the reference docs rather than hiding it on the page that you get to if you clickmodal.Function.While looking into this, I noticed that a few other objects were the only public object defined in their module, but we were for some reason configuring their reference to represent the module. This doesn't seem necessary; I removed it so that the references docs are more consistently formatted across types.
e.g., before:
and after:
Also, hey buddy 👋