Skip to content

Conversation

@wayneparrott
Copy link
Collaborator

Fix for issue #601.

time.js fromMsg()

  • fixed invalid nanoseconds property access
  • improved Time#fromMsg() jsdoc

time.d.ts fromMsg()

  • changed msg parameter type to builtin_interfaces.msg.Time
  • changed clockType parameter to optional
  • improved tsdoc

test-time.js

  • enhanced test to include Time#fromMsg()

@wayneparrott
Copy link
Collaborator Author

@minggangw I probably should have confirmed with you that this is a legit issue before opening it. I did not find any tests for the fromMsg() api and jumped to the conclusions cited as problems 1 and 2 in issue #601 behind this PR. Minimally 3rd issue needs to be fixed for use in typescript.

time.js fromMsg()
- fixed invalid nanoseconds property access
- improved Time#fromMsg() jsdoc

time.d.ts fromMsg()
- changed msg parameter type to builtin_interfaces.msg.Time
- changed clockType parameter to optional
- improved tsdoc
- ignore eslint camelcase rule on some lines to avoid false negatives

test-time.js
- enhanced test to include Time#fromMsg()
Copy link
Member

@minggangw minggangw left a comment

Choose a reason for hiding this comment

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

Thanks for correcting the name and LGTM!

@minggangw minggangw merged commit dbf130e into RobotWebTools:develop Mar 11, 2020
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.

2 participants