chore: bump to 1.1.0 - #39
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe pull request prepares the Flutter package for release 1.1.0. It adds a changelog entry for 1.1.0. The entry documents survey-interaction segment filter support, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Same class of finding Sonar raised on the Kotlin side (S1186): an empty function body needs the reason nested inside the braces. Pre-empting it here rather than waiting for the scan.
|



Release prep for #38.
Why minor, not patch
It adds a feature. Survey-interaction segment filters ("have seen X", "have completed X", …) did not work on Flutter before — the SDK kept using the segment list it received at app launch, so a rule like "completed survey A → show survey B" never fired in the same session.
Workspaces using interaction targeting get new traffic. One extra user-state request after a display, response or finish — gated per survey and per event, and routed through the
UpdateQueueso a burst debounces into a single request. Workspaces that don't use interaction targeting see no change at all, since the server omits the gate entirely for them.Unlike the native SDKs, there was no dormant timer bug to fix here —
expiry_tickerextends the user-state expiry rather than refetching, matchingjs-core. So baseline traffic for existing apps is unchanged.No public API changed.
lib/formbricks.dartstill exports onlyLogLevel,result.dart,errors.dartand theFormbrickswidget. The newTInteractionRefresh/InteractionSourcetypes, the addedFinishedEventvariant and theTSurvey.interactionRefreshfield all live underlib/src/, which is private by convention and not exported.Worth noting explicitly:
FinishedEventis a new variant of the sealedWebViewEvent, which would be a breaking change for any consumer writing an exhaustiveswitchover it. It is safe only because that class is not exported. IfWebViewEventis ever promoted to the public API, adding variants stops being a minor.Changes
packages/formbricks/pubspec.yaml:1.0.0→1.1.0packages/formbricks/CHANGELOG.md:1.1.0entry, in the existing formatThe playground depends on the package by
path, so nothing else needs updating.Verification
dart analyzeclean,dart formatclean, 308 tests passing.