Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

The metadata map is being re-populated on updates to the service #209

Open
jdelisle opened this issue Jul 22, 2014 · 3 comments
Open

The metadata map is being re-populated on updates to the service #209

jdelisle opened this issue Jul 22, 2014 · 3 comments

Comments

@jdelisle
Copy link

This causes issues with resources returning Json representations.

weierophinney:

@jdelisle Yes, please open an issue on zfcampus/zf-apigility-admin; basically, we shouldn't be re-populating the metadata map on updates to the service, and that's the problem you're having.

See zfcampus/zf-hal#38

@weierophinney
Copy link
Member

This will be harder than I thought to achieve. We actually do need to repopulate the metadata map in instances where the entity or collection are changed, or the hydrator. I'm not sure if we'll be able to resolve this; we may need to instead document workarounds.

@jdelisle
Copy link
Author

Okay, I'm going to go back to the alternative you suggested in zfcampus/zf-hal#38 (comment):

Create a different entity type in your service [than the one defined in the metadata map], and make sure your resource class returns entities using that type.

@michalbundyra
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools-admin; a new issue has been opened at laminas-api-tools/api-tools-admin#47.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants