Skip to content

Commit 83766ca

Browse files
committed
Merge branch '5.2' into 5.x
* 5.2: Tweaks Update DSN Update DSN Support JWT v4 Remove UuidBinary/UlidBinary usages from documentation
2 parents ff96759 + dc29127 commit 83766ca

File tree

3 files changed

+12
-23
lines changed

3 files changed

+12
-23
lines changed

components/uid.rst

Lines changed: 6 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -115,9 +115,8 @@ UUID objects created with the ``Uuid`` class can use the following methods
115115
Storing UUIDs in Databases
116116
~~~~~~~~~~~~~~~~~~~~~~~~~~
117117

118-
You can store UUID values as any other regular string/binary values in the database.
119-
However, if you :doc:`use Doctrine </doctrine>`, it's more convenient to use the
120-
special Doctrine types which convert to/from UUID objects automatically::
118+
If you :doc:`use Doctrine </doctrine>`, consider using the ``uuid`` Doctrine
119+
type, which converts to/from UUID objects automatically::
121120

122121
// src/Entity/Product.php
123122
namespace App\Entity;
@@ -134,11 +133,6 @@ special Doctrine types which convert to/from UUID objects automatically::
134133
*/
135134
private $someProperty;
136135

137-
/**
138-
* @ORM\Column(type="uuid_binary")
139-
*/
140-
private $anotherProperty;
141-
142136
// ...
143137
}
144138

@@ -166,7 +160,7 @@ entity primary keys::
166160

167161
.. versionadded:: 5.2
168162

169-
The UUID types and generators were introduced in Symfony 5.2.
163+
The UUID type and generators were introduced in Symfony 5.2.
170164

171165
When using built-in Doctrine repository methods (e.g. ``findOneBy()``), Doctrine
172166
knows how to convert these UUID types to build the SQL query
@@ -260,9 +254,8 @@ ULID objects created with the ``Ulid`` class can use the following methods::
260254
Storing ULIDs in Databases
261255
~~~~~~~~~~~~~~~~~~~~~~~~~~
262256

263-
You can store ULID values as any other regular string/binary values in the database.
264-
However, if you :doc:`use Doctrine </doctrine>`, it's more convenient to use the
265-
special Doctrine types which convert to/from ULID objects automatically::
257+
If you :doc:`use Doctrine </doctrine>`, consider using the ``ulid`` Doctrine
258+
type, which converts to/from ULID objects automatically::
266259

267260
// src/Entity/Product.php
268261
namespace App\Entity;
@@ -279,11 +272,6 @@ special Doctrine types which convert to/from ULID objects automatically::
279272
*/
280273
private $someProperty;
281274

282-
/**
283-
* @ORM\Column(type="ulid_binary")
284-
*/
285-
private $anotherProperty;
286-
287275
// ...
288276
}
289277

@@ -310,7 +298,7 @@ entity primary keys::
310298

311299
.. versionadded:: 5.2
312300

313-
The ULID types and generator were introduced in Symfony 5.2.
301+
The ULID type and generator were introduced in Symfony 5.2.
314302

315303
When using built-in Doctrine repository methods (e.g. ``findOneBy()``), Doctrine
316304
knows how to convert these ULID types to build the SQL query

mercure.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -423,10 +423,10 @@ And here is the controller::
423423
{
424424
$hubUrl = $this->getParameter('mercure.default_hub');
425425
$this->addLink($request, new Link('mercure', $hubUrl));
426-
426+
427427
$key = Key\InMemory::plainText('mercure_secret_key'); // don't forget to set this parameter! Test value: !ChangeMe!
428428
$configuration = Configuration::forSymmetricSigner(new Sha256(), $key);
429-
429+
430430
$token = $configuration->builder()
431431
->withClaim('mercure', ['subscribe' => ["http://example.com/books/1"]]) // can also be a URI template, or *
432432
->getToken($configuration->signer(), $configuration->signingKey())

notifier.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Service Package DSN
5959
========== ================================ ====================================================
6060
Esendex ``symfony/esendex-notifier`` ``esendex://USER_NAME:PASSWORD@default?accountreference=ACCOUNT_REFERENCE&from=FROM``
6161
FreeMobile ``symfony/free-mobile-notifier`` ``freemobile://LOGIN:PASSWORD@default?phone=PHONE``
62-
Infobip ``symfony/infobip-notifier`` ``infobip://TOKEN@default?from=FROM``
62+
Infobip ``symfony/infobip-notifier`` ``infobip://ACCESS_TOKEN@HOST?from=FROM``
6363
Iqsms ``symfony/iqsms-notifier`` ``iqsms://LOGIN:PASSWORD@default?from=FROM``
6464
Mobyt ``symfony/mobyt-notifier`` ``mobyt://USER_KEY:ACCESS_TOKEN@default?from=FROM``
6565
Nexmo ``symfony/nexmo-notifier`` ``nexmo://KEY:SECRET@default?from=FROM``
@@ -144,15 +144,16 @@ integration with these chat services:
144144

145145
========== ================================ ===========================================================================
146146
Service Package DSN
147+
<<<<<<< HEAD
147148
========== ================================ ===========================================================================
148149
Discord ``symfony/discord-notifier`` ``discord://TOKEN@default?webhook_id=ID``
149150
GoogleChat ``symfony/google-chat-notifier`` ``googlechat://ACCESS_KEY:ACCESS_TOKEN@default/SPACE?threadKey=THREAD_KEY``
150151
LinkedIn ``symfony/linked-in-notifier`` ``linkedin://TOKEN:USER_ID@default``
151-
Mattermost ``symfony/mattermost-notifier`` ``mattermost://TOKEN@ENDPOINT?channel=CHANNEL``
152+
Mattermost ``symfony/mattermost-notifier`` ``mattermost://ACCESS_TOKEN@HOST/PATH?channel=CHANNEL``
152153
RocketChat ``symfony/rocket-chat-notifier`` ``rocketchat://TOKEN@ENDPOINT?channel=CHANNEL``
153154
Slack ``symfony/slack-notifier`` ``slack://TOKEN@default?channel=CHANNEL``
154155
Telegram ``symfony/telegram-notifier`` ``telegram://TOKEN@default?channel=CHAT_ID``
155-
Zulip ``symfony/zulip-notifier`` ``zulip://EMAIL:APIKEY@ENDPOINT?channel=CHANNEL``
156+
Zulip ``symfony/zulip-notifier`` ``zulip://EMAIL:TOKEN@HOST?channel=CHANNEL``
156157
========== ================================ ===========================================================================
157158

158159
.. versionadded:: 5.1

0 commit comments

Comments
 (0)