Added metadata definition for chat.postMessage and history

[tchapuis]

The Slack documentation says that we can include metadata in chat.postMessage arguments. See : https://api.slack.com/metadata

OpenApi spec for this argument doesn't seem to be up to date.

So I added it to the patched version for message definition and chat.postMessage method. I also added the include_all_metadata argument for the conversations.history method

[yngc0der]

The temporary solution is create a custom endpoint class, and use this class to call api method:

<?php

use JoliCode\Slack\Api\Endpoint\ChatPostMessage;

final class FixedChatPostMessageEndpoint extends ChatPostMessage
{
    protected function getFormOptionsResolver(): \Symfony\Component\OptionsResolver\OptionsResolver
    {
        $optionsResolver = parent::getFormOptionsResolver();
        $optionsResolver->setDefined(['metadata']);
        $optionsResolver->setAllowedTypes('metadata', ['string']);
        return $optionsResolver;
    }
}


$slack->executeEndpoint(new FixedChatPostMessageEndpoint([
    'channel' => $channel,
    'text' => $text,
    'metadata' => $metadata,
]));

[damienalexandre]

Hello, sorry for the very long delay on the review.

I fear the ".patch" file is wrong, it includes A LOT of changes that have nothing to do with the metadata definition 🤔 Maybe it's just because Slack updated their definition, but we should then split this in two PR.

Thank you for your understanding 🙏

[tchapuis]

Hello,
The patch file was a pain to get it right 😅

[damienalexandre]

Thanks for working on this!

Tests on main were red, so I fixed them in #162 ;
could you please:

• rm -rf generated/
• vendor/bin/jane-openapi generate --config-file=.jane-openapi.php

And push?

[damienalexandre]

Awesome, thank you so much!

[damienalexandre]

Version v4.6.0 is published!