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

Add Event Descriptions #46

Open
wants to merge 90 commits into
base: main
Choose a base branch
from
Open

Add Event Descriptions #46

wants to merge 90 commits into from

Conversation

Yadunund
Copy link
Member

This PR adds Descriptions for items listed in #43

Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
@Yadunund Yadunund marked this pull request as ready for review November 17, 2021 10:31
@Yadunund
Copy link
Member Author

@mxgrey this is ready for review. There were some linker errors when compiling and hence I had to implement rmf_task_sequence::detail::Backup and some inherited functions in rmf_task_sequence::Task. For the latter I have left most of it as TODOs.

@mxgrey mxgrey self-requested a review November 18, 2021 03:11
@mxgrey mxgrey self-assigned this Nov 25, 2021
Signed-off-by: Michael X. Grey <[email protected]>
Copy link
Contributor

@mxgrey mxgrey left a comment

Choose a reason for hiding this comment

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

This is only a partial review with some comments of things that I think could be tweaked.

Overall this PR is looking good.


//==============================================================================
/// Store contact details for telecommunication
class ContactCard
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see why this class would be in a detail namespace. If it gets touched by a user of the library then it should be in a normal public API namespace. If it doesn't get touched by a user of the library then we should keep it inside of src/ and we don't need to pimpl it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Moved to events namespace fb34755

{
public:

struct PhoneNumber
Copy link
Contributor

Choose a reason for hiding this comment

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

We should pimpl this class if it's in the public API.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done fb34755

const std::string& name,
const std::string& address,
const std::string& email,
PhoneNumber number);
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if some of these fields should be optional. I suppose an empty string could imply that it's unknown, but I always prefer having the "null type" as an entirely separate object type for explicitness.

Copy link
Member Author

Choose a reason for hiding this comment

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

Made address and email optional fb34755

using DescriptionPtr = std::shared_ptr<Description>;
using ConstDescriptionPtr = std::shared_ptr<const Description>;

class Model;
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of a custom Call::Model we can just use WaitFor::Description::make_model and return its result for Call::Description::make_model.

Copy link
Member Author

Choose a reason for hiding this comment

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

Using WaitFor::Model for Call and SMS fb34755


/// Make a PerformAction description.
///
/// \param[in] action_name
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of an action name, I wonder if we should just accept an entire JSON payload to pass along to the command handle, and allow either side of the pipeline to do whatever they want with it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done fb34755

mxgrey and others added 17 commits December 7, 2021 13:41
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Michael X. Grey <[email protected]>
Signed-off-by: Yadunund <[email protected]>
Base automatically changed from redesign_v2 to main February 13, 2022 16:56
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