Support Maghrib angle offset

[vadiole]

Hello!

For some calculation methods (Jafari, Tahran) Maghrib time is calculated later than sunset.

Please add an option to specify offset angle for Maghrib

Source

[ahmedre]

I believe today, this isn't supported even in adhan-swift, @z3bi can confirm though.

[vadiole]

This looks like a commit in which this parameter was added to swift version, @ahmedre please take a look:
batoulapps/adhan-swift@205af60

[vadiole]

I could make a pull request with the necessary changes. Can you confirm that you will be able to merge it and release a new version?

[ahmedre]

please hold off - my intention is to go through the Swift code again and "catch up" the missing features since that's not the only thing missing at the moment.

[vadiole]

Yes, indeed.
I offer my help in adding this setting because I use this wonderful library and due to the lack of this setting some of my users are getting the wrong time for Maghrib.

I could port the logic that is already in swift for java if you would be willing to accept my PR. If you implement it on your own in the near future, I can wait a bit. My main intention is that I would like to provide my users with the correct Maghrib time as soon as possible, and I don't mind contributing to this library.

[ahmedre]

thank you - will prioritize this in sha' Allah.

[vadiole]

Hello, any updates on this issue?

[ahmedre]

PR #63 brings Adhan Kotlin up to date with Adhan Swift, with the exception of the Maghrib angle offset feature. After consideration, we unfortunately will not be adding this feature to the Kotlin / Java libraries, because it is against the consensus of the scholars on the definition of when Maghrib is.

[vadiole]

I respect your decision, however some locations use this kind of offset to calculate Madhrib. I still can use some other solution, if you are not willing to add this option.

At least you might want to close this as "won't do", as the feature is still missing.

Btw, are there plans to remove this feature for swift version?

[ahmedre]

I spoke with @z3bi (author / maintainer of the Swift version), and he has no plans to remove it from the Swift version