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

APP-3104: Fluent OBO API for services #284

Merged
merged 7 commits into from
Oct 14, 2020
Merged

APP-3104: Fluent OBO API for services #284

merged 7 commits into from
Oct 14, 2020

Conversation

symphony-elias
Copy link
Contributor

@symphony-elias symphony-elias commented Oct 12, 2020

Ticket

APP-3104

Description

Implemented Fluent API for OBO endpoints

Checklist

  • Referenced a ticket in the PR title and in the corresponding section
  • Filled properly the description and dependencies, if any
  • Unit tests updated or added
  • Javadoc added or updated
  • Updated the documentation in docs folder

Copy link
Member

@thibauult thibauult left a comment

Choose a reason for hiding this comment

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

That was pretty fast :)

@@ -55,18 +41,14 @@
*/
@Slf4j
@API(status = API.Status.STABLE)
public class MessageService {
public class MessageService extends OboMessageService {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm a bit afraid of inheritance bringing problems later as it introduces a lot of coupling, do we have use cases where you would need the message service to be used either as OBO or not OBO (i.e the need to have a common parent class/interface)

Have we looked at existing bots to see how they use OBO and if they mix OBO / non OBO usages?

Copy link
Member

Choose a reason for hiding this comment

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

Composition instead of inheritance? We could consider using https://projectlombok.org/features/Delegate.html

@symphony-elias symphony-elias marked this pull request as ready for review October 13, 2020 13:50
@symphony-elias symphony-elias requested a review from a team October 13, 2020 13:50
@symphony-youri
Copy link
Contributor

👍 for the interface approach

@symphony-youri
Copy link
Contributor

Let's push it further with the Spring Boot integration (or in a separate PR if you prefer)

Copy link
Member

@thibauult thibauult left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@symphony-elias symphony-elias merged commit e5646c2 into finos:master Oct 14, 2020
@symphony-elias symphony-elias deleted the APP-3104 branch October 20, 2020 13:43
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