You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a specific reason why all attributes of a message are private and there are no accessor methods? Would be really helpful to be able to read these values. I'll submit a pull request if its welcome. Wanted to know the thinking behind this decision before doing it though.
Also, it seems that a text version of the message is required. Every time I try to send a message with just an HTML body I get "Message not valid". Another conscious decision? The Mailgun API doesn't suggest that this is required and to my knowledge it shouldn't be.
The text was updated successfully, but these errors were encountered:
I think that the original design was aimed at "fire and forget" - which made messages more short lived. I agree that accessor methods would be an improvement - a PR is welcome.
Regarding the required text message along with HTML - I quickly glanced at the documentation and it doesn't say anything about requiring text body along with HTML. Have you, by any change, tested this? If tests confirm proper behaviour with no text body a PR is also more than welcome.
Is there a specific reason why all attributes of a message are private and there are no accessor methods? Would be really helpful to be able to read these values. I'll submit a pull request if its welcome. Wanted to know the thinking behind this decision before doing it though.
Also, it seems that a text version of the message is required. Every time I try to send a message with just an HTML body I get "Message not valid". Another conscious decision? The Mailgun API doesn't suggest that this is required and to my knowledge it shouldn't be.
The text was updated successfully, but these errors were encountered: