Skip to content

Conversation

@pmattmann
Copy link
Member

Loading a single CampCollaboration does not always seem performant - but is used very often.

image

I think, we don't need to embed the Camp there.
When a single CampCollaboration is loaded, the Camp is probably already in the cache.

@BacLuc
Copy link
Contributor

BacLuc commented Mar 29, 2025

Cool.
In #6461 (comment) we said we would make even more for this endpoint.

@pmattmann
Copy link
Member Author

Cool. In #6461 (comment) we said we would make even more for this endpoint.

For CampCollaboration-Item it says:
image

Of course we will change more... one PR after the other 😉

'groups' => ['read', 'CampCollaboration:User'],
'swagger_definition_name' => 'read',
];
public const COLLECTION_NORMALIZATION_CONTEXT = [
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need the embedding of the camp in the collection request?

@pmattmann pmattmann requested a review from a team April 2, 2025 17:08
@pmattmann pmattmann force-pushed the feature/perf-camp-collaboration-item-endpoint branch from a39f14c to 7cd5d23 Compare April 11, 2025 21:52
@pmattmann pmattmann enabled auto-merge April 11, 2025 21:52
@pmattmann pmattmann added this pull request to the merge queue Apr 11, 2025
Merged via the queue into ecamp:devel with commit d2c55d0 Apr 11, 2025
30 checks passed
@pmattmann pmattmann deleted the feature/perf-camp-collaboration-item-endpoint branch April 11, 2025 22:00
@carlobeltrame carlobeltrame mentioned this pull request Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants