Hello, There's been an issue in using scoop that has seemingly creat

Thanks for the contribution <a class="user-mention notranslate" data-hovercard-type="u

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

This has been addressed in <a href="https://github.com/olivertappin/scoop/releases/tag

Publishing content_type is always text/plain about scoop HOT 3 CLOSED

olivertappin commented on August 23, 2024

Publishing content_type is always text/plain

from scoop.

Comments (3)

olivertappin commented on August 23, 2024

Thanks for the contribution @andrefigueira 🎉

Absolutely. This is a good feature request and I'm happy to get this in.

I'll review the code shortly and get back to you.

from scoop.

olivertappin commented on August 23, 2024

@andrefigueira after thinking about this in detail, I'm thinking we should remove it as an option, and simply read the existing message content type instead? Scoop was built as a dumb consumer, so modifying the message in any way is sort of outside the scope of what Scoop should be used for. What do you think?

from scoop.

olivertappin commented on August 23, 2024

This has been addressed in 2.1.0. More specifically, we are ensuring all the various parts of the message are passed on to the publisher. For more information, see these lines.

from scoop.

Recommend Projects