Skip to content
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

Fix validation of YouTubeVideoBlock #2260

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

thomasdax98
Copy link
Member

Previously, the validation of the YouTubeVideoBlock differed between admin and API.
The admin allowed YouTube URLs and YouTube video IDs.
The API only allowed URLs but blocked video IDs.

Now, the API validation also accepts URLs and video IDs.


PR Checklist

  • Verify if the change requires a changeset. See CONTRIBUTING.md
  • Link to the respective task if one exists: COM-898

@thomasdax98 thomasdax98 force-pushed the fix-youtube-block-api-validation branch from 63388f5 to 6e9c3c7 Compare July 5, 2024 09:35
@johnnyomair johnnyomair merged commit c7f5637 into main Jul 8, 2024
11 checks passed
@johnnyomair johnnyomair deleted the fix-youtube-block-api-validation branch July 8, 2024 06:04
@johnnyomair johnnyomair mentioned this pull request Jul 8, 2024
thomasdax98 added a commit that referenced this pull request Jul 9, 2024
Previously, the validation of the `YouTubeVideoBlock` differed between
admin and API.
The admin allowed YouTube URLs and YouTube video IDs.
The API only allowed URLs but blocked video IDs.

Now, the API validation also accepts URLs and video IDs.
fichtnerma pushed a commit that referenced this pull request Jul 18, 2024
Previously, the validation of the `YouTubeVideoBlock` differed between
admin and API.
The admin allowed YouTube URLs and YouTube video IDs.
The API only allowed URLs but blocked video IDs.

Now, the API validation also accepts URLs and video IDs.
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.

2 participants