Skip to content

fix: correct config chaining in withIntercomPushNotification PR#383

Open
Rosie-Kennelly-1 wants to merge 1 commit intomainfrom
rosie/fix-push-notification-plugin-chaining
Open

fix: correct config chaining in withIntercomPushNotification PR#383
Rosie-Kennelly-1 wants to merge 1 commit intomainfrom
rosie/fix-push-notification-plugin-chaining

Conversation

@Rosie-Kennelly-1
Copy link

@Rosie-Kennelly-1 Rosie-Kennelly-1 commented Mar 6, 2026

Why?

towards: https://github.com/intercom/intercom/issues/360467

withIntercomPushNotification passes the original config to each sub-plugin instead of the chained result, so modifications from earlier plugins in the chain are silently dropped.

How?

Pass newConfig instead of config so each plugin receives the output of the previous one.

Split out from:
#384
#385

Generated with Claude Code

The exported plugin was passing the original `config` to both
`appDelegate` and `infoPlist` instead of the chained `newConfig`,
which meant each plugin received the unmodified config rather than
the result of the previous plugin in the chain.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Rosie-Kennelly-1 Rosie-Kennelly-1 changed the title fix: correct config chaining in withIntercomPushNotification fix: correct config chaining in withIntercomPushNotification PR (1/3) Mar 6, 2026
@Rosie-Kennelly-1 Rosie-Kennelly-1 changed the title fix: correct config chaining in withIntercomPushNotification PR (1/3) fix: correct config chaining in withIntercomPushNotification PR Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants