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

Pass ResourceMetadata instead of $resourceShortName in OperationPathR… #790

Closed
wants to merge 2 commits into from

Conversation

amenophis
Copy link
Contributor

@amenophis amenophis commented Oct 7, 2016

Q A
Bug fix? no
New feature? yes
BC breaks? yes
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR api-platform/docs#121

Pass ResourceMetadata instead of $resourceShortName in OperationPathResolvers

@amenophis amenophis force-pushed the allow-global-config branch 3 times, most recently from f136fbd to 5143904 Compare October 7, 2016 13:15
Copy link
Contributor

@teohhanhui teohhanhui left a comment

Choose a reason for hiding this comment

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

This is not a good way to do it. We should only provide string $resourceClass. Then you can get the ResourceMetadata yourself.

/cc @dunglas

@amenophis
Copy link
Contributor Author

@teohhanhui What is the problem ? The ResourceMetadata is already loaded, why not allow to pass it directly ?

@teohhanhui
Copy link
Contributor

teohhanhui commented Oct 10, 2016

@amenophis "Already loaded" is merely an implementation detail. We make the interface harder to implement and use if we pass the ResourceMetadata object. It's also extra overhead forced upon those who don't need it.

@dunglas
Copy link
Member

dunglas commented Mar 20, 2017

Can we close this one?

@teohhanhui teohhanhui closed this Mar 20, 2017
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.

None yet

4 participants