You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDK now leverages PHP 8.2+ `#[SensitiveParameter]` attributes to enhance security by preventing sensitive data
29
-
from appearing in stack traces and error logs. This affects methods that handle:
45
+
The SDK now leverages PHP 8.2+ `#[SensitiveParameter]` attributes to enhance security
46
+
by preventing sensitive data from appearing in stack traces and error logs.
47
+
This affects methods that handle:
30
48
31
49
- Passwords and authentication credentials
32
50
- JWT tokens (ID tokens, refresh tokens, custom tokens)
@@ -36,44 +54,95 @@ from appearing in stack traces and error logs. This affects methods that handle:
36
54
## Dependency Changes
37
55
38
56
### PSR Log Dependency
39
-
`psr/log` is now a development dependency instead of a runtime dependency. This change reduces the production dependency footprint. If you were using PSR Log interfaces directly in your application code, you should add `psr/log` to your project's composer.json.
57
+
58
+
`psr/log` is now a development dependency instead of a runtime dependency.
59
+
This change reduces the production dependency footprint.
60
+
If you were using PSR Log interfaces directly in your application code,
61
+
you should add `psr/log` to your project's composer.json.
40
62
41
63
### Removed Constants
42
-
The `Kreait\Firebase\Contract\Messaging::BATCH_MESSAGE_LIMIT` constant has been removed. If you were using this constant in your code, you should define the limit (500) in your application or use the Firebase messaging service limits documentation as reference.
64
+
65
+
The `Kreait\Firebase\Contract\Messaging::BATCH_MESSAGE_LIMIT` constant has been removed.
66
+
If you were using this constant in your code,
67
+
you should define the limit (500) in your application or use the Firebase messaging service limits documentation as reference.
43
68
44
69
### Exception Handling Changes
45
-
Exception codes are no longer preserved when wrapping exceptions. If your code relies on specific exception codes for error handling, you should update it to use exception types or messages instead.
46
70
47
-
### Cloud Message Builder Method Renames
71
+
Exception codes are no longer preserved when wrapping exceptions.
72
+
If your code relies on specific exception codes for error handling,
73
+
you should update it to use exception types or messages instead.
48
74
49
-
The `CloudMessage` builder methods for setting message targets have been renamed to follow the `with*` naming pattern for consistency with other builder methods in the SDK:
75
+
### Cloud Message Builder Method Renames
50
76
51
-
-`toToken()` -> `withToken()`
52
-
-`toTopic()` -> `withTopic()`
53
-
-`toCondition()` -> `withCondition()`
77
+
The `CloudMessage` builder methods for setting message targets have been renamed
78
+
to follow the `with*` naming pattern for consistency with other builder methods in the SDK.
54
79
55
80
**Migration:**
56
81
57
-
Replace the old method names with the new ones:
82
+
```diff
83
+
-$message = CloudMessage::new()
84
+
- ->toToken('device-token')
85
+
- ->withNotification(['title' => 'Hello']);
86
+
+$message = CloudMessage::new()
87
+
+ ->withToken('device-token')
88
+
+ ->withNotification(['title' => 'Hello']);
89
+
90
+
-$message->toTopic('news');
91
+
+$message->withTopic('news');
92
+
93
+
-$message->toCondition("'dogs' in topics");
94
+
+$message->withCondition("'dogs' in topics");
95
+
```
96
+
97
+
The old methods are still available as deprecated aliases,
98
+
so your code will continue to work during the transition period.
99
+
100
+
### Removed Factory Methods
58
101
59
-
```php
60
-
// Before (7.x)
61
-
$message = CloudMessage::new()
62
-
->toToken('device-token')
63
-
->withNotification(['title' => 'Hello']);
102
+
Several debugging and logging methods have been removed from the `Factory` class.
0 commit comments