Skip to content

Draft: Centralize Input/Output and Data Class Logic in Metadata#7908

Closed
Cafeine42 wants to merge 5 commits into
api-platform:mainfrom
Cafeine42:input-output-idea
Closed

Draft: Centralize Input/Output and Data Class Logic in Metadata#7908
Cafeine42 wants to merge 5 commits into
api-platform:mainfrom
Cafeine42:input-output-idea

Conversation

@Cafeine42

Copy link
Copy Markdown
Contributor
Q A
Branch? main
Tickets Closes #..., closes #...
License MIT

ould we store string-class|null directly instead of an array that may contain class?
Does getClass become unnecessary? We still need input/output/data, which could default to the API resource class when undefined.

@Cafeine42 Cafeine42 force-pushed the input-output-idea branch 3 times, most recently from def8e4e to 7766881 Compare April 11, 2026 22:35
@Cafeine42 Cafeine42 force-pushed the input-output-idea branch 2 times, most recently from bea6c55 to 4506f77 Compare June 21, 2026 09:16
@Cafeine42 Cafeine42 force-pushed the input-output-idea branch from 4506f77 to ac1b635 Compare June 21, 2026 14:58
@soyuka

soyuka commented Jun 22, 2026

Copy link
Copy Markdown
Member

I don't understand what are you trying to achieve?

@Cafeine42

Copy link
Copy Markdown
Contributor Author

Replace by #8338

@Cafeine42 Cafeine42 closed this Jun 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Centralize Input/Output and Data Class Logic in Metadata

3 participants