5
5
[ ![ GitHub Code Style Action Status] ( https://img.shields.io/github/actions/workflow/status/ziming/laravel-statsig/fix-php-code-style-issues.yml?branch=main&label=code%20style&style=flat-square )] ( https://github.com/ziming/laravel-statsig/actions?query=workflow%3A"Fix+PHP+code+style+issues"+branch%3Amain )
6
6
[ ![ Total Downloads] ( https://img.shields.io/packagist/dt/ziming/laravel-statsig.svg?style=flat-square )] ( https://packagist.org/packages/ziming/laravel-statsig )
7
7
8
- Laravel Package for Statsig. A Feature Gate & A/B Testing Platform with a somewhat decent free tier.
8
+ Laravel Package for Statsig. A Feature Gate & A/B Testing Platform with a somewhat decent free tier
9
9
10
- This package is still very early in development & likely not ready for production use yet.
11
- I have only just started using it in production on 2 small sites currently.
10
+ This package is still very early in development, but I have used it on a few small production sites for a while already.
12
11
13
- Use at your own risk if you want to try it now. But if you have used in production, it would be great to let me know :)
12
+ If you have used in production, it would be great to let me know any feedback :)
14
13
15
14
It is basically a wrapper around the [ Statsig PHP SDK] ( https://docs.statsig.com/server/phpSDK )
16
15
@@ -20,7 +19,7 @@ The following features are being considered for the future. If any of it interes
20
19
21
20
- New Adapters
22
21
- New Middlewares
23
- - Convenience Traits & Methods
22
+ - More Convenience Traits & Methods
24
23
- HTTP & Console API support
25
24
- Octane/Vapor/Serverless Support (Probably far in the future)
26
25
@@ -120,8 +119,8 @@ LaravelStatsigUserConfiguration::setConversionCallable(function (User $laravelUs
120
119
121
120
// Lastly you can also use LaravelStatsigEvent instead of StatsigEvent
122
121
// as it accepts a laravel user object
123
- // I recommend the object action event naming framework
124
- // https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/
122
+ // See Useful References at the end of the read me for some best practices to follow for events naming conventions
123
+
125
124
$statsigEvent = new LaravelStatsigEvent('event_name');
126
125
127
126
// You can also use this convenience method
@@ -158,6 +157,20 @@ Like the blade directive, currently it can only be used if the user is logged in
158
157
``` bash
159
158
composer test
160
159
```
160
+ ## Userful References
161
+
162
+ Below are links to some good reads that I think would benefit you in getting started:
163
+
164
+ ### Feature Gates
165
+ - https://www.statsig.com/blog/feature-gates-101
166
+
167
+ ### Sample Sizes
168
+ - https://blog.statsig.com/you-dont-need-large-sample-sizes-to-run-a-b-tests-6044823e9992
169
+ - https://www.statsig.com/blog/intro-to-sample-size
170
+
171
+ ### Event Naming Best Practices
172
+ - https://segment.com/academy/collecting-data/naming-conventions-for-clean-data/
173
+ - https://davidwells.io/blog/clean-analytics
161
174
162
175
## Changelog
163
176
0 commit comments