4.2.0

Overview

This release focuses on improving code quality, type safety, and developer experience by introducing PHPStan static analysis, fixing deprecated patterns, and modernizing the codebase to leverage PHP 8.1+ features.

Added

• Added PHPStan with maximum level analysis for strict type checking
• Implemented PHPStan strict rules, deprecation rules, and PHPUnit extensions
• Created two analysis configurations:
  • phpstan.neon - For PHP 8.1 compatibility
  • phpstan-future.neon - For PHP 8.5 forward compatibility

Improved

• Enhanced type safety across the entire codebase with PHPDoc annotations
• Improved return type declarations throughout the SDK
• Added comprehensive type hints for arrays and mixed types
• Improved method chaining return types
• Enhanced documentation with PHPDoc type annotations
• Better memory usage in batch operations
• Added comprehensive type hints for better IDE support

4.1.2

Fixed

• Segment hit collection: Resolved API format issue in bucketing mode where context values weren't properly serialized as strings, causing hits to be rejected by the collection endpoint

4.1.1

Fixed

• Troubleshooting : Prevent sending troubleshooting hits when troubleshooting is not activated on NO_BATCHING_AND_CACHING_ON_FAILURE strategy

3.2.2

Fixed

• Troubleshooting : Prevent sending troubleshooting hits when troubleshooting is not activated on NO_BATCHING_AND_CACHING_ON_FAILURE strategy

4.1.0

Added

• Batch Limit for Activate Hits — Implemented a fixed maximum limit on activate hits per batch, significantly reducing network overhead while maintaining analytics accuracy.

Improved

• Contextual Segment Hits — In bucketing mode, segment hits are now only sent when the visitor context has been updated, reducing unnecessary network requests and improving performance.

Fixed

• Allocation Consistency Issue — Fixed a bug in the variation allocation algorithm that incorrectly added variations with allocation 0 in BUCKETING mode

4.0.1

Fixed

• Activate hit in non consent mode

4.0.0

Add

• Visitor Status
• Flag status
• Visitor->getFlags method
• The onSdkStatusChanged properties in SDK configuration

Change

• visitor->getFlag method signature
• Flag->getValue method signature
  -hasConsented property when creating a visitor is now mandatory
• SDK status enum
• Require now php >= 8.1

Remove

• From visitor instance (modifications, getFlagsDataArray, getModificationsArray, getModification, getModificationSync, getModificationInfo, getModificationInfoSync, synchronizeModifications, and activateModification)
• From SDK configuration (statusChangedCallback)

3.2.1

Improved

• Usage data collection process

3.2.0

Added

• Collecting developer usage tracking data:
  • Troubleshooting data collection can now be enabled with your agreement by Flagship services in the SDK for debugging purposes.
  • Usage data collection is now enabled in the SDK, which will help us improve our product.
• setDisableDeveloperUsageTracking accessor in FlagshipConfig class

3.1.3

Added

• getCampaignName, getVariationGroupName and getVariationName in Flag metadata