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): add missing attributes for CT Source update #2792

Merged
merged 4 commits into from
Feb 27, 2024

Conversation

damcou
Copy link
Contributor

@damcou damcou commented Feb 27, 2024

🧭 What and Why

🎟 JIRA Ticket: DI-1788

Changes included:

  • Add missing attributes url and fallbackIsInStockValue for CT Source Update

@damcou damcou requested a review from a team as a code owner February 27, 2024 10:52
Copy link

netlify bot commented Feb 27, 2024

Deploy Preview for api-clients-automation ready!

Name Link
🔨 Latest commit 1dae7fe
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/65ddd693128eac000897b6ee
😎 Deploy Preview https://deploy-preview-2792--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 configuration.

@damcou damcou requested a review from Fluf22 February 27, 2024 10:53
@algolia-bot
Copy link
Collaborator

algolia-bot commented Feb 27, 2024

✗ 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.

Comment on lines 378 to 382
fallbackIsInStockValue:
type: boolean
default: true
description: >
Determines the value that will be stored in the Algolia record if there's no inventory information on the product.
Copy link
Contributor

Choose a reason for hiding this comment

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

This means during an update, it will default to true...
Are you sure this is the wanted behavior?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With the dashboard, the value should always be sent, but you're right, let's remove the default value on update

Copy link
Contributor

Choose a reason for hiding this comment

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

Then you should add it to the required array

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor Author

Choose a reason for hiding this comment

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

(and removed, see below)

Copy link
Member

Choose a reason for hiding this comment

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

This means during an update, it will default to true... Are you sure this is the wanted behavior?

We don't (and shouldn't) use default values in the API client, if the API defaults to true it's normal to mention it here

Copy link
Member

Choose a reason for hiding this comment

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

ah it's an update nvm

customFields:
$ref: '#/CommercetoolsCustomFields'
required:
Copy link
Collaborator

Choose a reason for hiding this comment

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

the goal of the update is not to have required properties

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed, please, I just want to close my PR about the custom fields...

Copy link
Member

@shortcuts shortcuts left a comment

Choose a reason for hiding this comment

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

wonderful

@damcou damcou merged commit d48e2f6 into main Feb 27, 2024
26 checks passed
@damcou damcou deleted the fix/source-update-ct branch February 27, 2024 12:50
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.

5 participants