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(modeldetails): renamed the property to the expected value #895

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

lprovost-coveo
Copy link
Contributor

@lprovost-coveo lprovost-coveo commented Dec 12, 2024

Property was wrongly baptised, expected property name is
image

Technically it's not a breaking change since the property mapped to nothing before, and so changing the name doesn't break the change since nothing points to nothing

Acceptance Criteria

  • My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
  • JSDoc annotates each property added in the exported interfaces
  • The proposed changes are covered by unit tests
  • Commits containing breaking changes a properly identified as such
  • README.md is adjusted to reflect the proposed changes (if relevant)
  • My merge commit message will be conventional (See Conventional Commit)

@lprovost-coveo lprovost-coveo added this pull request to the merge queue Dec 13, 2024
Merged via the queue into master with commit fecf9a9 Dec 13, 2024
6 checks passed
@lprovost-coveo lprovost-coveo deleted the fix/MLX-1749-fix-property-name branch December 13, 2024 19:33
Copy link

🎉 This PR is included in version 57.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants