MarkEmbling.PostcodesIO icon indicating copy to clipboard operation
MarkEmbling.PostcodesIO copied to clipboard

.NET library for interacting with the excellent Postcodes.io service.

Results 7 MarkEmbling.PostcodesIO issues
Sort by recently updated
recently updated
newest added

Right now, testing is pretty much reliant on hitting the live API in integration tests. This needs to change so all the independent bits of behaviour (e.g. deserialisation of results)...

Why is "ced" not available in PostcodeResult? When we lookup ex. OX14 3PF we would like to use. "Abingdon East". When we use Postcodes.io website this is returned in ced,...

Move these out so they can be swapped out for more testing without hitting a live API. Also will prevent duplication for #11.

The Postcodes.io API will return a 404 response when querying for a postcode which doesn't exist (and so on across the various endpoints). Ensure these are handled in an unsurprising,...

Test that all fields are used correctly. Same for bulk reverse geocoding.

Currently the API returns `null` for some query endpoints where no results/matches exist, and for others it returns `[]`. This can't be changed for backwards-compatibility reasons (see https://github.com/ideal-postcodes/postcodes.io/issues/319). However it...

There are a massive (and growing, see #10) number of methods on `PostcodesIOClient`. These need to be split up in logical groups. The best approach is probably to mirror the...