workaround: getting collection on update fragment Request
I am keeping a track here so can be clear what was the reason of that workaround
Problem: When an update on fragment happens there is no way to get the Collection of a fragment. The api call is a PATCH : /collections/:collectionId/fragments/:fragmentId and that returns only the id of fragment which is not enough in order to get the relationship between fragment and collection.
The workaround is to pass the project to the request which in turns will return that object at the response.