Closed tomsabin closed 10 years ago
Thanks for making us aware. That's definitely not the exception it should be raising. It should be raising IdealPostcodes::LimitReachedError and IdealPostcodes::TokenExhaustedError respectively.
We just pushed an update (0.1.1) which should fix that problem. Also added much needed documentation on error handling.
This wrapper is definitely getting a bit long in the tooth now, so we'll spend some time this week pushing more updates. No breaking changes - mainly adding the newer API methods, updating dependencies and enabling CI.
@tomsabin - hopefully everything is working fine. Let me know if not. Otherwise I will close issue #1 end of today. Thanks
Perfect, thanks for the swift response @cblanc. I have updated to 0.1.1 and all is working as intended.
ideal_postcodes (0.1.0)
rails (4.1.5)
ruby-2.1.2
As documented under the "testing" heading in https://ideal-postcodes.co.uk/documentation, the following two postcodes break the gem:
Daily usage (
ID1 CHOP
)No lookups remaining (
ID1 CLIP
)