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

Provide an API to interact with CalDav server #1462

Open
HoussemNasri opened this issue Jan 15, 2025 · 1 comment · May be fixed by #1465
Open

Provide an API to interact with CalDav server #1462

HoussemNasri opened this issue Jan 15, 2025 · 1 comment · May be fixed by #1465
Assignees

Comments

@HoussemNasri
Copy link
Member

What?

To implement #1329, we need to interact with the CalDav server in order to get/set event attendance status. This ticket is preliminary work for the mentioned ticket.

How?

Introduce DavClient which encapsulates CardDav and CalDav operations used in other parts of the codebase.

public interface DavClient {
    Mono<Boolean> existsCollectedContact(String username, String userId, String collectedId);

    Mono<Void> createCollectedContact(String username, String userId, CardDavCreationObjectRequest creationObjectRequest);

    Mono<PartStat> getUserParticipationStatus(String userId, String eventUuid);

    Mono<Void> setUserParticipationStatus(String userId, String eventUuid, PartStat partStat);
}

Definition of done

Integration tests for getUserParticipationStatus and setUserParticipationStatus

@HoussemNasri HoussemNasri self-assigned this Jan 15, 2025
@HoussemNasri HoussemNasri linked a pull request Jan 15, 2025 that will close this issue
@chibenwa
Copy link
Member

eventUuid => eventUid As I recall I do not think the spec mandates a uuid, just a globally unique identifier.

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 a pull request may close this issue.

2 participants