Using the ChatPostMessagePayload, I am unable to set the bot I've created as the sender. I'm setting the username of a bot I've created as the username, but messages are still posted as the slackbot. I can see from the documentation that the API supports an as_user parameter which might be useful since I'm authenticating with the API token of the bot, but it appears that the repository does not support this.

Fatal error: Uncaught exception 'Doctrine\Common\Annotations\AnnotationException' with message '[Semantical Error] The annotation "@JMS\Serializer\Annotation\Type" in property CL\Slack\Payload\ChatPostMessagePayload::$channel does not exist, or could not be auto-loaded.' in [...path...]/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationException.php:54
Stack trace:
#0 [...path...]/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/DocParser.php(708): Doctrine\Common\Annotations\AnnotationException::semanticalError('The annotation ...')
#1 [...path...]/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/DocParser.php(641): Doctrine\Common\Annotations\DocParser->Annotation()
#2 [...path...]/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/DocParser.php(334): Doctrine\Common\Annotations\DocParser->Annotations()
#3 [...path...]/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationReader.p in [...path...]/vendor/cleentfaar/slack/CL/Slack/Transport/ApiClient.php on line 108

I have confirmed that the Type.php file is there in the right location and the right namespace, and composer can load it through its autoloader - however the Doctrine Annotations library bypasses the standard PHP autoloading mechanism for some reason, and you have to register annotations with the AnnotationRegistry. I'm sure the JMSSerializer library must have done this, and 'use'ing the namespace and aliasing it as you are doing in ChatPostMessagePayload is supposed to fix this (use JMS\Serializer\Annotation as Serializer), so I'm unsure why this is happening myself. I'm not very familiar with the JMS Serializer library though.

Firstly, your library looks great and I am looking forward to using it.

Could you possibly update your usage documentation in line with your latest changes?

I've tried to get up and running but am getting stuck with:

Catchable fatal error: Argument 2 passed to CL\Slack\Transport\ApiClient::__construct() must be an instance of CL\Slack\Util\PayloadSerializer, none given, called in C:\inetpub\wwwroot\src\SD\SOS\Console\Check.php on line 19 and defined in C:\inetpub\wwwroot\vendor\cleentfaar\slack\src\CL\Slack\Transport\ApiClient.php on line 78

I can see that you've added a PayloadSerializer param to ApiClient but can't seem to pass it the right thing.

e.g. I've tried:

$payloadSerialiazer = new \CL\Slack\Util\PayloadSerializer();
$client = new \CL\Slack\Transport\ApiClient($apiToken, $payloadSerializer);

But no luck.

You also give the example of $payload->setMessage(), but this is depreciated in favour of $payload->setText()?

After running compose update guzzlehttp/guzzle package got updated to 6.0.1 and effectively broke sending messages. I fixed it by fixing it at version 5.3.0 in my composer.json.

I don't know what has changed in guzzle package but you have to restrict it to version below 6.0.0 or make it compatible with new version.

Documentation for the added properties: https://api.slack.com/events/message

Subtype

Unlike other event types, message events can have a subtype

Attachments

Messages can also include an attachments property, containing a list of attachment objects. https://api.slack.com/docs/attachments

@cleentfaar: Resolves #11

Although there may be an issue with an included library not correctly declaring their own dependencies, friction can and should be reduced for users of the "cleentfaar/slack" package by masking them from this problem and taking the issue up separately with any maintainers of the underlying dependency libraries.

Wonderful library you have - thanks for considering the patch!

This removes the dependency on annotations for serialization of objects (now using yaml mapping).

I've also added almost all of the tests that were (still) missing, and fixed a lot of hidden bugs.

todo:

• [x] Stamp out as much bugs as possible
• [x] Add the (missing) tests for all payloads and responses
• [x] Add the missing tests for the models

I have oAuth2 working and would like to post a message as an authenticated user.

Would like to try and patch this myself but at a loss as where to get started.

When you called the messages.search API method, the JMS serializer throw an error "you should define a type of permalink". So I fixed that and every error which occurred later.

method used: chat.postMessage

When I try to post a message with attachments, the attachments are not 'seen' by the slack service. I tried encoding them to json prior to sending them to slack via a guzzle event listener like this:

$guzzle->getEmitter()->on('before', function (BeforeEvent $before) {
    $body = $before->getRequest()->getBody();
    $attachments = $body->getField('attachments');
    $body->setField('attachments', json_encode($attachments));
});

And got what I expected (a chat message with attachments). However, this leads me to think there is something wrong with the serialization process of nested payload entries.

In short, my findings:

//does not work
[
    'attachments' => [
        ['title' => 'hello world']
    ]
]

//does work
[
    'attachments' => "[{'title': 'hello world'}]"
]

Hi Cas,

I noticed that the CL\Slack\Serializer\ModelSerializer class is never integrated in the library. It exists, but none of the other parts are calling it. Except for the AbstractModelTest class which uses it to test the getters of the models.

I was wondering if you plan to use it in the library or if it's merely there for testing purposes.

Thx!

Matthias

• Installation request for cleentfaar/slack ^0.20.1 -> satisfiable by cleentfaar/slack[0.20.1].
• Conclusion: remove symfony/event-dispatcher v4.1.6
• Conclusion: don't install symfony/event-dispatcher v4.1.6

How can I detect messages such as "xy has joined the channel", "xy set the channel purpose", and similar, which are not really composed by a person but rather Slack? Unfortunately, the username and userId given in SimpleMessage are the same, no matter if its a message from a human being or Slack in the name of the human being. Is there a sensible way to detect what kind of message it is?

This is mapped as a string but is actually returned as an object from Slack and causes the deserialisation of the API response to throw a SlackException exception with the message "Array to string conversion".

https://github.com/cleentfaar/slack/blob/ba7073cb79ccea423cd68f6a69096384a730a013/src/CL/Slack/Resources/config/serializer/CL.Slack.Model.File.yml#L82

initial_comment is actually this format:

{id: "Fc80KCQ5MF",
created: 1510793564,
timestamp: 1510793564,
user: "U8167JE7P",
is_into: true,
comment: "Blah blah blah"
}

Added properties to the abstract class of response payload for scope that needed to complete the requested method and scopes that provided by application. Added explanation for error 'missing_scope' that includes details about needed scope and scopes, provided by the application.

Hi @cleentfaar

The Yaml dependency appears to be fixed under 3.0, and hence I cannot port a bundle I'm working on to Symfony 4 :)

Would you mind to add this support?

Thank you