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

Implement datatypes into sagittarius protocol #17

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Taucher2003
Copy link
Member

Closes #10

@Taucher2003 Taucher2003 force-pushed the 10-implement-datatypes-for-sagittarius branch from 68dbe87 to 559f6e1 Compare November 18, 2024 20:39
FUNCTION = 7;
}

shared.Translation name = 1;
Copy link
Member Author

Choose a reason for hiding this comment

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

Should we use a map<string, string> instead of a repeated object?

Copy link
Member

Choose a reason for hiding this comment

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

I think an object is more readable and easier to understand

Copy link
Member Author

Choose a reason for hiding this comment

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

The messages could probably also be useful for the communication between Aquila and the actions. Should we move them to shared and only keep the service here?

Copy link
Member

Choose a reason for hiding this comment

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

Move them into shared

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.

Implement DataTypes in sagittarius protocol
2 participants