Skip to content

Added POPO acronym where first explained #1174

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 3, 2020
Merged

Added POPO acronym where first explained #1174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion core/design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Since you only need to describe the structure of the data to expose, API Platfor
API framework. However, the "design-first" methodology is strongly recommended: first you design the **public shape** of
API endpoints.

To do so, you have to write a plain old PHP object representing the input and output of your endpoint. This is the class
To do so, you have to write a plain old PHP object (POPO) representing the input and output of your endpoint. This is the class
that is [marked with the `@ApiResource` annotation](../distribution/index.md).
This class **doesn't have** to be mapped with Doctrine ORM, or any other persistence system. It must be simple (it's usually
just a data structure with no or minimal behaviors) and will be automatically converted to [Hydra](extending-jsonld-context.md),
Expand Down