feat(specs): introduce multifeed composition behavior for beta release by gavinwade12 · Pull Request #5828 · algolia/api-clients-automation

gavinwade12 · 2026-01-15T20:51:20Z

🧭 What and Why

This PR introduces the new multifeed composition behavior. It should currently be released in beta / privately / whatever we did prior to our GA launch.

🎟 JIRA Ticket: CMP-709 + Slack thread for more context

Changes included:

Add multifeed behavior schema
Add specific types for each case of behavior: compositionInjectionBehavior and compositionMultifeedBehavior
Change compositionBehavior to be oneOf the two preceding types, meaning the injection and multifeed fields within the behavior object are mutually exclusive

🧪 Test

Green CI
yarn cli generate javascript compositions yields valid results i.e. the new types exist + are correct and CompositionBehavior is now a union of the two specific behavior types (CompositionInjectionBehavior | CompositionMultifeedBehavior)

algolia-bot · 2026-01-15T20:51:36Z

✔️ Code generated!

Name	Link
🪓 Triggered by	`74901440ac8b4a486a14d92c5e62ce6598c757a3`
🍃 Generated commit	`a66724cfe98bb979118cd7c692776308c4b724c2`
🌲 Generated branch	`generated/feat/compositions/multifeed-behavior-beta`

📊 Benchmark results

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

Language	Req/s
javascript	2447
go	2205
php	1890
csharp	1499
python	1362
java	1183
ruby	879
swift	637
scala	23

ClaraMuller

Small comment,
Not approving just because I believe we don't want to merge now but good for me 👍
Having a look why we have a breaking change 🤷‍♀️

ClaraMuller · 2026-01-16T09:15:31Z

specs/composition/common/schemas/components/multifeed/Behaviour.yml

+      description: A key-value store of Feed ID to Feed. Currently, the only supported Feed type is an Injection.
+      additionalProperties:
+        $ref: '../injection/Behaviour.yml#/injection'
+    feedsOrder:


Can you add an example ?

I added one, but I couldn't figure out how to get the generated doc page, e.g. this, locally to see if it looked correct

ClaraMuller · 2026-01-16T09:19:16Z

2026-01-15T20:56:49.1476928Z ***! MODIFIED INTERFACE (<- CLASS) : PUBLIC ABSTRACT (<- NON_ABSTRACT) com.algolia.model.composition.CompositionBehavior  (not serializable)
2026-01-15T20:56:49.1477709Z 	===  CLASS FILE FORMAT VERSION: 52.0 <- 52.0
2026-01-15T20:56:49.1478342Z 	===  UNCHANGED SUPERCLASS: java.lang.Object (<- java.lang.Object)
2026-01-15T20:56:49.1479291Z 	---! REMOVED CONSTRUCTOR: PUBLIC(-) CompositionBehavior()
2026-01-15T20:56:49.1480310Z 	---! REMOVED METHOD: PUBLIC(-) com.algolia.model.composition.Injection getInjection()
2026-01-15T20:56:49.1481951Z 	---! REMOVED METHOD: PUBLIC(-) com.algolia.model.composition.CompositionBehavior setInjection(com.algolia.model.composition.Injection)
2026-01-15T20:56:49.1483480Z +++  NEW CLASS: PUBLIC(+) FINAL(+) kotlin.collections.builders.SerializedCollection  (changed from Serializable to Externalizable)
2026-01-15T20:56:49.1484593Z 	+++  CLASS FILE FORMAT VERSION: 52.0 <- n.a.
2026-01-15T20:56:49.1485419Z 	+++  NEW SUPERCLASS: java.lang.Object
2026-01-15T20:56:49.1557087Z ##[group]Run rm -rf tests/output/java/src/test/java/com/algolia/client tests/output/java/src/test/java/com/algolia/requests tests/output/java/src/test/java/com/algolia/e2e tests/output/java/src/test/java/com/algolia/benchmark || true
2026-01-15T20:56:49.1559019Z �[36;1mrm -rf tests/output/java/src/test/java/com/algolia/client tests/output/java/src/test/java/com/algolia/requests```

ClaraMuller · 2026-01-16T09:21:30Z

@Fluf22 How we can remove te breaking change ? Because this update will still be done when we will actually release the feature ?

gavinwade12 · 2026-01-16T12:02:27Z

@Fluf22 How we can remove te breaking change ? Because this update will still be done when we will actually release the feature ?

There's a breaking change because I made the behaviors mutually exclusive using oneOf, which changes the types a bit.

If we don't want a breaking change, I can make it so, but it'll be possible to set both behaviors at once at the client level, which is invalid. I think it's only a breaking change for some languages, like Go, that can't handle oneOf as nicely as e.g. JavaScript.

ClaraMuller · 2026-01-16T13:44:48Z

it'll be possible to set both behaviors at once at the client level, which is invalid.

In my mind this is not a good solution but I am not the expert on that topic so I'll let api client team choose what is the best solution.

Fluf22 · 2026-01-16T16:23:35Z

Ultimately, it's your call: if the first feature is currently used, we shouldn't do a breaking change. If that's necessary, we will have to add a notice like I did last time
If the feature isn't used yet, I guess it's okay to make a BC then

gavinwade12 · 2026-01-16T19:55:32Z

I just pushed a commit that changes to a less-strict typing, so there should be less breaking changes. There may still be some since injection is no longer required within a behavior, so Injection → *Injection in some languages.

I noticed we have the same issue for the batch endpoint, where we could actually be even stricter with the types at the client level. I think we should open a separate PR for stricter typing, especially since this isn't meant to be released publicly yet.

#5828) (generated) [skip ci] Co-authored-by: Gavin Wade <gavin.wade12@gmail.com>

…e (generated) algolia/api-clients-automation#5828 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Gavin Wade <gavin.wade12@gmail.com>

gavinwade12 requested a review from a team as a code owner January 15, 2026 20:51

gavinwade12 changed the title ~~feat(compositions): introduce multifeed behavior for beta release~~ feat(specs): introduce multifeed composition behavior for beta release Jan 15, 2026

ClaraMuller reviewed Jan 16, 2026

View reviewed changes

ClaraMuller requested review from Fluf22 and e-krebs January 16, 2026 09:21

ClaraMuller requested a review from a team January 16, 2026 09:21

ClaraMuller previously approved these changes Jan 19, 2026

View reviewed changes

gavinwade12 force-pushed the feat/compositions/multifeed-behavior-beta branch from 9f23ab7 to b74b391 Compare January 20, 2026 12:55

Fluf22 force-pushed the feat/compositions/multifeed-behavior-beta branch from b74b391 to 827900a Compare January 20, 2026 15:57

gavinwade12 added 3 commits January 20, 2026 16:58

feat(compositions): introduce multifeed behavior for beta release

bae0cfe

feat: add example

6dd2ff0

fix: be less strict so there are no/less breaking changes

91415cb

Fluf22 force-pushed the feat/compositions/multifeed-behavior-beta branch from 827900a to 91415cb Compare January 20, 2026 15:58

chore: beta marker

ab3e5be

Fluf22 dismissed ClaraMuller’s stale review via ab3e5be January 20, 2026 16:12

Fluf22 force-pushed the feat/compositions/multifeed-behavior-beta branch from a81d3ff to ab3e5be Compare January 20, 2026 16:12

Fluf22 requested a review from a team as a code owner January 20, 2026 16:12

Fluf22 requested a review from eric-zaharia January 20, 2026 16:12

Fluf22 approved these changes Jan 20, 2026

View reviewed changes

Fluf22 merged commit f9ac3a7 into main Jan 20, 2026
37 checks passed

Fluf22 deleted the feat/compositions/multifeed-behavior-beta branch January 20, 2026 16:40

algolia-bot added a commit that referenced this pull request Jan 20, 2026

feat(specs): introduce multifeed composition behavior for beta release (

746ad29

#5828) (generated) [skip ci] Co-authored-by: Gavin Wade <gavin.wade12@gmail.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(specs): introduce multifeed composition behavior for beta release#5828

feat(specs): introduce multifeed composition behavior for beta release#5828
Fluf22 merged 4 commits intomainfrom
feat/compositions/multifeed-behavior-beta

gavinwade12 commented Jan 15, 2026 •

edited by atlassian bot

Loading

Uh oh!

algolia-bot commented Jan 15, 2026 •

edited

Loading

Uh oh!

ClaraMuller left a comment

Uh oh!

ClaraMuller Jan 16, 2026

Uh oh!

gavinwade12 Jan 16, 2026

Uh oh!

ClaraMuller commented Jan 16, 2026

Uh oh!

ClaraMuller commented Jan 16, 2026 •

edited

Loading

Uh oh!

gavinwade12 commented Jan 16, 2026 •

edited

Loading

Uh oh!

ClaraMuller commented Jan 16, 2026

Uh oh!

Fluf22 commented Jan 16, 2026

Uh oh!

gavinwade12 commented Jan 16, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

gavinwade12 commented Jan 15, 2026 • edited by atlassian bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧭 What and Why

Changes included:

🧪 Test

Uh oh!

algolia-bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✔️ Code generated!

Uh oh!

ClaraMuller left a comment

Choose a reason for hiding this comment

Uh oh!

ClaraMuller Jan 16, 2026

Choose a reason for hiding this comment

Uh oh!

gavinwade12 Jan 16, 2026

Choose a reason for hiding this comment

Uh oh!

ClaraMuller commented Jan 16, 2026

Uh oh!

ClaraMuller commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gavinwade12 commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ClaraMuller commented Jan 16, 2026

Uh oh!

Fluf22 commented Jan 16, 2026

Uh oh!

gavinwade12 commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

gavinwade12 commented Jan 15, 2026 •

edited by atlassian bot

Loading

algolia-bot commented Jan 15, 2026 •

edited

Loading

ClaraMuller commented Jan 16, 2026 •

edited

Loading

gavinwade12 commented Jan 16, 2026 •

edited

Loading

gavinwade12 commented Jan 16, 2026 •

edited

Loading