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: populate anyOf only if we have options #2643

Merged
merged 2 commits into from
Jan 3, 2025

Conversation

Sepehr-Sobhani
Copy link
Contributor

Copy link
Contributor

@pbastia pbastia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! We might want to add a test that we can render the page properly with an empty array

Signed-off-by: SeSo <sobhani.sepehr@gmail.com>
Signed-off-by: SeSo <sobhani.sepehr@gmail.com>
@Sepehr-Sobhani Sepehr-Sobhani force-pushed the 2624-fix-new-contact-new-operation branch from 1310aff to 1a1f585 Compare January 3, 2025 19:44
@Sepehr-Sobhani
Copy link
Contributor Author

Nice! We might want to add a test that we can render the page properly with an empty array

@pbastia Thank you for reviewing this PR! We already had tests for the contact form, and we should have caught that error earlier if we had been using the correct schema to render the component. By using the appropriate schema, an error was raised, and I was able to fix it. I added an extra test for the operation form to ensure it's working as expected.

@Sepehr-Sobhani Sepehr-Sobhani merged commit ad97a58 into develop Jan 3, 2025
42 checks passed
@Sepehr-Sobhani Sepehr-Sobhani deleted the 2624-fix-new-contact-new-operation branch January 3, 2025 20:41
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