Skip to content

refactor(metadata): cascade resource to operation #7246

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

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

soyuka
Copy link
Member

@soyuka soyuka commented Jun 26, 2025

Also related to #7213

Adds a way to update your operations without having to do it manually (only when values are null but are set on the api resource).

This code would also make a refactoring possible inside our current metadata factories.

@soyuka soyuka force-pushed the feat/casacde-to-op branch 3 times, most recently from e4d9ddd to e938d53 Compare June 27, 2025 10:16
@soyuka soyuka changed the title feat(metadata): cascade resource to operation refactor(metadata): cascade resource to operation Jun 27, 2025
@soyuka soyuka force-pushed the feat/casacde-to-op branch from e938d53 to 936e4f9 Compare June 27, 2025 10:23
@soyuka soyuka force-pushed the feat/casacde-to-op branch from 936e4f9 to c5c0d7e Compare June 27, 2025 13:05
@soyuka soyuka merged commit fb96f33 into api-platform:main Jun 27, 2025
110 of 112 checks passed
@soyuka
Copy link
Member Author

soyuka commented Jun 27, 2025

Finally took some time to fix also the type hint on getOperations that will now return proper HttpOperation !

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.

1 participant