Skip to content

feat(specs): update transformation specs for no-code #4901

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

Merged
merged 6 commits into from
Jun 3, 2025

Conversation

mehmetaligok
Copy link
Contributor

@mehmetaligok mehmetaligok commented May 30, 2025

🧭 What and Why

We are updating the transformation endpoints to support the upcoming no-code transformations.

Changes included:

  • Both request and response formats updated.
  • type field added with an enum.
  • input field added for both types.

NOTE: The no-code input is left as a generic input because there is a need for recursion, but the generation doesn't seem to work properly for this complex structure.

We expect this to be used internally, so we will move forward with a generic field for now.

@mehmetaligok mehmetaligok self-assigned this May 30, 2025
@algolia-bot
Copy link
Collaborator

algolia-bot commented May 30, 2025

💥 Breaking changes detected !!

Either this PR or a previous PR not released yet introduced breaking changes, be careful when merging.
You can find the details in the 'client java@17' CI job.

✔️ Code generated!

Name Link
🪓 Triggered by d009f85b203faa9683adbe3717ac0d42a93acd60
🍃 Generated commit dc928011fb9da675a526657e790df3550ba42cd2
🌲 Generated branch generated/feat/update-transformation-specs-for-no-code
📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language Req/s
go 1790
javascript 1647
php 1518
csharp 1320
java 1101
python 1024
ruby 801
swift 397
scala 23

@mehmetaligok mehmetaligok changed the title feat(spec): update transformation specs for no-code feat(specs): update transformation specs for no-code May 30, 2025
@mehmetaligok mehmetaligok force-pushed the feat/update-transformation-specs-for-no-code branch from 17411b4 to a945a1c Compare June 2, 2025 08:35
@mehmetaligok mehmetaligok marked this pull request as ready for review June 2, 2025 15:15
@mehmetaligok mehmetaligok requested a review from a team as a code owner June 2, 2025 15:15
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.

nice

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.

perfect gg!

@shortcuts shortcuts merged commit 06ad06e into main Jun 3, 2025
28 checks passed
@shortcuts shortcuts deleted the feat/update-transformation-specs-for-no-code branch June 3, 2025 10:03
algolia-bot added a commit that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-csharp that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-go that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-java that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-javascript that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-kotlin that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-php that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-python that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-ruby that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-scala that referenced this pull request Jun 3, 2025
algolia-bot added a commit to algolia/algoliasearch-client-swift that referenced this pull request Jun 3, 2025
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