Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Hello,

This is my first poll so do not hesitate to tell me if I am wrong.

I have a special use case for the notifier using the iSendPro transport. I have some data to pass to iSendPro that are not available at this time in the framework so I wanted to discuss here if they can be added like in the other transport or if it is not the way to go.

Relating to the official documentation we can send some option that can be useful for to track the sms or be aware of the context.
By example:

nb_sent_sms?: int,
noStop?: bool,
sendAt?: \DateTimeImmutable,
utf8?: bool,
tracker?: string

Theses are the ones I see that can be helpful to the community but if you do see others we can discuss about it.
Anyways to avoid the break changes they shall be added as optional with the current behavior remaining as default.

I have prepared the code to make some tests on my project so if the community is ok with it I can open a PR with the changes.

Will it be useful to add all or part of the suggested options to iSendPro transport ?
All of them are fine
0%
This transport is not likely to be enhanced
0%
Just a part of the options are relevant
0%
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
Morty Proxy This is a proxified and sanitized view of the page, visit original site.