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

ApiPlatform: change design to expose API through standalone class and use DataProvider and DataPersister #117

Open
Rebolon opened this issue Feb 6, 2019 · 2 comments · Fixed by #118

Comments

@Rebolon
Copy link
Owner

Rebolon commented Feb 6, 2019

Here is the documentation about this:

The problem with current implementation is that ApiPlatform and Doctrine share everything, which could be a problem if we don't want to expose some properties to Api.
In complexe legacy app it cuols be hard to use ApiPlatform with the current implementation. So the separation of concern is, once again, a good thing !

Now the problem is how to implement this ???

Rebolon pushed a commit that referenced this issue Feb 11, 2019
Rebolon added a commit that referenced this issue Feb 11, 2019
…nnotat… (#118)

* Try to use DataProvider instead of auto-binding with Doctrine annotations

* fix partially #117
@Rebolon Rebolon reopened this Feb 11, 2019
@Rebolon
Copy link
Owner Author

Rebolon commented Feb 11, 2019

Should not be closed because !118 is only a POC for DataProvider usage

@Rebolon
Copy link
Owner Author

Rebolon commented Feb 18, 2019

It must also show how to use:

  • pagination in this pattern (Provider and object returned by Persister)
  • sort
  • filter like search
  • return only wished params

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant