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

Extract APIs (not implementation) from jmap-extensions module into their own maven module #1254

Open
HoussemNasri opened this issue Oct 21, 2024 · 1 comment · May be fixed by #1339
Open
Assignees
Labels
good first issue Good for newcomers

Comments

@HoussemNasri
Copy link
Member

Currently, the contact search engine, models, and related event bus infrastructure are located within the jmap-extensions module. This is not ideal as building anything on top of the contacts module requires depending on jmap-extensioons a completely unrelated and quite large module.

@chibenwa
Copy link
Member

Add a new maven module:

tmail-backend/jmap/extensions-api

Relocate in there traits and interfaces that extensions-* projects needs.

definition of done

These projects shall not depend on tmail-backend/jmap/extensions

@HoussemNasri HoussemNasri changed the title Extract the contact data model into its own maven module Extract APIs (not implementation) from jmap-extensions module into their own maven module Nov 26, 2024
@HoussemNasri HoussemNasri self-assigned this Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
2 participants