Use configured message limit when creating serializers

[Wirone]

When message_limit is set in Raven client options, serializers should use this value instead of default message limit from RAVEN_Client::MESSAGE_LIMIT.

[stayallive]

Yes, yes they should! Thanks 😄

[Jean85]

Do we need to fix the same thing on 2.0? @ste93cry ?

[ste93cry]

There is not anymore a message_limit configuration option in 2.0: I'm not sure about why i've removed it, maybe because the limit was hardcoded anyway in Sentry server anyway or because I've decided to cleanup a bit the amount of options we had. Anyway since 2.0 the limit is enforced in the MessageInterfaceMiddleware middleware as you can see below, so the best thing users can do to change it is to create their own middleware. I would like to avoid at all costs to add more options than necessary like in 1.x where we have a huge amount of them

sentry-php/lib/Raven/Middleware/MessageInterfaceMiddleware.php

Line 43 in a39bb02

$event = $event->withMessage(substr($message, 0, Client::MESSAGE_MAX_LENGTH_LIMIT), $messageParams);