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(specs): correct type for renderingContent and consequenceParams #759

Merged
merged 4 commits into from
Jun 27, 2022

Conversation

shortcuts
Copy link
Member

🧭 What and Why

🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-554

Changes included:

  • renderingContent type and properties were wrong
    • this parameter is also used in the consequence params field, which was missing here
  • consequence was missing some params parameters and had wrong types

🧪 Test

CI :D

@shortcuts shortcuts self-assigned this Jun 27, 2022
@shortcuts shortcuts marked this pull request as draft June 27, 2022 10:26
@algolia-bot
Copy link
Collaborator

algolia-bot commented Jun 27, 2022

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.
You can still access the code generated on main via this commit.

@netlify
Copy link

netlify bot commented Jun 27, 2022

Deploy Preview for api-clients-automation ready!

Name Link
🔨 Latest commit 0a393fb
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/62b9aed7fd5412000885d3aa
😎 Deploy Preview https://deploy-preview-759--api-clients-automation.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@shortcuts shortcuts force-pushed the fix/specs-renderingContent-consequence branch from 6a14111 to 1c4b9c6 Compare June 27, 2022 10:33
@shortcuts shortcuts requested review from a team, damcou and millotp and removed request for a team June 27, 2022 10:47
@shortcuts shortcuts marked this pull request as ready for review June 27, 2022 10:47
Copy link
Collaborator

@millotp millotp left a comment

Choose a reason for hiding this comment

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

I'm not sure about my comments because the description is in the generated code, but according the openapi spec a $ref should always be alone

specs/search/paths/rules/common/schemas.yml Outdated Show resolved Hide resolved
automaticOptionalFacetFilters:
type: object
description: Same syntax as automaticFacetFilters, but the engine treats the filters as optional.
Copy link
Collaborator

Choose a reason for hiding this comment

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

same as above

Copy link
Member Author

Choose a reason for hiding this comment

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

idk if the description will work for this ref, but will see!

Copy link
Collaborator

Choose a reason for hiding this comment

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

looks like it's working, it's still weird ahah

@shortcuts shortcuts requested a review from millotp June 27, 2022 13:46
@shortcuts shortcuts merged commit 7a85822 into main Jun 27, 2022
@shortcuts shortcuts deleted the fix/specs-renderingContent-consequence branch June 27, 2022 15:34
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.

3 participants