-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
RestFul API - fix and upgrade description #778
Comments
I think this upgrade will allow to be closer to sf5 and it should be done. But, what do you think if in the future we move to Api platform generated api? It seems to be more updated and we will have better support? wdyt? This movement is being done in sylius too: Sylius/Sylius#11250 @sonata-project/contributors |
IMHO STEP 1 should be release as fast as possible. Other things can wait as long as Symfony5 is not support. |
List of
|
STEP 2 is ready but need be merge in some order, otherwise travis will not install rest-bundle v3:
then NewsBundle and ecommerce can be merge. @greg0ire Can you help with releases? |
I update this issue. I think we have pattern to resolve this issue (based on my tests and your nelmio support). IMHO we should spit it to 3 PR for each bundle:
@phansys Can you finish UserBundle? I will working on it in Thursday. |
I think after the merge of sonata-project/SonataUserBundle#1198, I can rebase sonata-project/SonataUserBundle#1186. |
What's the status of this ? |
The api is getting deprecated. I think we can close this. |
Current RestFul API is autdated and should be updated.
'REST'
routing type is deprecated,friendsofsymfony/rest-bundle
andnelmio/api-doc-bundle
should be upgrade to allow use Symfony5. Will be nice to add functional tests too, to keep it working in feature.Work description
fix router unavailable resource
In this scope some controller services will be added to allow import routing from
REST
type. It is quick fix for current REST API.drop
'REST'
routing type in favor for xmlREST
routing type is deprecated. Before another change it must be replace by other type. In Sonata we are usingxml
so this type should be used in API too.support for
friendsofsymfony/rest-bundle
v3Add support, some pedantic change in commets/docblock.
Update Swagger definition in order to be compatible with string identifiers
This RPs will allow use other type than current
int
.string
will allow use other type too.[BC-break] improve models for swagger
We can consider 2 cases.
API
based directly on urls.Here BC will be keep.
Here BC will not be keep. Anyway provide empty interfaces as OAS models is also unhelpful. Provide BC-break in this case (for fix bad code) is nessessery. OAS should return end entity with people jms dictionary for it. (example)
Conclusion:
OAS model for user should:
Sonata\UserBundle\Model\UserInterface
toApp\Entity\SonataUserUser
src\Resources\config\serializer\Entity.SonataUserUser.xml
(by recipies)TODO:
'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3Update Swagger definition in order to be compatible with string identifiersnelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3'REST'
routing type in favor for xmlfriendsofsymfony/rest-bundle
v3nelmio/api-doc-bundle
v3also TODO
Sandbox for API tests
sonata-project/sandbox#629
This issue is create based on @phansys work in:
The text was updated successfully, but these errors were encountered: