Skip to content
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

DOCS-2035: Add example snippets to movement sensor, power sensor, sensor #230

Merged
merged 2 commits into from
Jun 17, 2024

Conversation

JessamyT
Copy link
Contributor

No description provided.

@JessamyT JessamyT requested a review from a team as a code owner June 13, 2024 00:22
Copy link
Member

@purplenicole730 purplenicole730 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realized there was also effort to standardize the comments, so I added some small nits. Otherwise, LGTM!

lib/src/components/power_sensor/power_sensor.dart Outdated Show resolved Hide resolved
lib/src/components/power_sensor/power_sensor.dart Outdated Show resolved Hide resolved
@@ -18,31 +18,72 @@ abstract class MovementSensor extends Resource {
static const Subtype subtype = Subtype(resourceNamespaceRDK, resourceTypeComponent, 'movement_sensor');

/// Obtain the measurements/data specific to this [MovementSensor]
/// If a sensor is not configured to have a measurement or fails to read a piece of data, it will not appear in the readings dictionary.
/// If a sensor is not configured to have a measurement or fails to read a piece of data,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: comment seems long compared to others

Future<Position> position({Map<String, dynamic>? extra});

/// Get the current linear velocity as a [Vector3] with x, y, and z axes represented in mm/sec
/// Get the current linear velocity as a [Vector3] with x, y, and z axes represented in mm/sec.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: comment is long compared to others

@JessamyT
Copy link
Contributor Author

@purplenicole730 Ooh I was unaware of this standardization. I personally don't see a problem with some comments being longer than others, since some methods require more explanation and some are highly self-explanatory. I'd like to leave those as they are if that's okay?

@purplenicole730
Copy link
Member

@JessamyT
No, there's no real standardization, but I was only pointing them out in case you cared, since I saw you were adding periods to some comments, and making new lines in others.

@JessamyT JessamyT merged commit 542e18b into viamrobotics:main Jun 17, 2024
3 checks passed
@JessamyT JessamyT deleted the 2030pwrmvmntsensor branch June 17, 2024 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants