-
Notifications
You must be signed in to change notification settings - Fork 24
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
RSDK-7962: organize sections in docs #266
RSDK-7962: organize sections in docs #266
Conversation
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.
LGTM if y'all are happy with this, thanks!
@@ -6,6 +6,7 @@ import '../../resource/manager.dart'; | |||
import '../../utils.dart'; | |||
import 'arm.dart'; | |||
|
|||
/// {@category Components} |
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.
All of the category definitions in all of the service.dart
files are actually unneeded since we don't export these files, so no documentation exists for these
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.
(No need to do anything, just commenting here for documentation)
Jira ticket
There are three new topics, "Components", "Services", and "Common". Component/service classes were moved out of the "Viam SDK" category.
The common library is auto generated, so the
export_protos.dart
file checks for the common library and adds it to the new "Common" topic instead of "Protobuf Definitions" topic. You can only have one category at a time.Unfortunately, setting the category for specific classes seems to happen at class definition, so the "Common" topic would have to be set in the auto-generated file. Defining the category while exporting common classes (in
lib/viam_sdk.dart
) did not work. I thought it should have, but I'm running into issues during testing this.There is an alternative, but less ideal, method of bringing attention to specific
common
classes.Common.md
links the common classes that are specifically in the Viam SDK library.Note: I did try using the
subCategories
to put everything under the Viam SDK category, but that doesn't seem to change the actual visuals based on what I've read and my own testing.