CC-37354 Glue RestAPI Migration Phase 1/2#3590
Conversation
✅ Deploy Preview for spryker-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…/cc-37354/master-glue-rest-api-migration-phase-1
…/cc-37354/master-glue-rest-api-migration-phase-1
…/cc-37354/master-glue-rest-api-migration-phase-1
…/cc-37354/master-glue-rest-api-migration-phase-1
…n for API Platform migration.
…/cc-37354/master-glue-rest-api-migration-phase-1
stereomon
changed the title
| link: docs/dg/dev/architecture/api-platform/troubleshooting.html | ||
| --- | ||
|
|
||
| API Platform automatically converts all exceptions into JSON:API formatted error responses. This includes domain errors thrown by Providers and Processors, validation failures, authentication errors, and unexpected exceptions. |
There was a problem hiding this comment.
I don't see example of the unexpected exceptions.
My main concern - how to avoid leak of internal error messages?
There was a problem hiding this comment.
I don't see example of the unexpected exceptions.
Unexpected can be anything. What should be used as an example here?
API Platform handles also exception as described here https://api-platform.com/docs/core/errors/
We also have our own subscriber for certain exceptions but in general there should be no internal excption message leaking.
| } | ||
| ``` | ||
|
|
||
| `AbstractRelationshipResolver` provides the following helpers: |
There was a problem hiding this comment.
what about merchant, agent, user.
I'm not 100% sure how you built the initial list, I did my best guess.
There was a problem hiding this comment.
We can't share all of them with the outside by default. The ones listed here are system defaults.
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
2 participants
PR Description
Migration guides for: https://release.spryker.com/release-groups/view/6425
Tickets
Checklist