cranst0n

@spebbe Any chance you can take a look at this? There are a few open PRs, and previously merged ones that would be great to have in a new release....

Okay no worries. I don't have a strong opinion on this one. I noticed an open issue and went for it. I personally don't see a huge downside to their...

Best guess is the type inference, or lack thereof, is causing issues. Try adding this to your 'analysis_options.yaml` file if it's not already in there: ```yaml analyzer: language: strict-inference: true...

Yep understandable. I think re-implementing the parsing shouldn't be too awful, at least for the basic types. I'll try throwing something minimal together and get a better feel for how...

@tpolecat I've reworked it and wanted to get an initial opinion from you if this direction seems okay to you. I'm jumping in the deep on PostGIS. Seems like being...

So I'm almost apologetic about this, but the scope of this expanded far more than I originally intended. Some of this probably isn't necessary to take on in skunk and...

FWIW, I hacked together some codecs that seem to behave for a few of the PostGIS types [in this gist](https://gist.github.com/cranst0n/1f14309690a82912396fc4e42ab713d3). Maybe of use for a legit PR down the road.

So the codecs in my gist are apparently for the built in postgres geometry types and _not_ PostGIS. So while they may be useful in some capacity, they're not what...

Did my best to resurrect this. Appears to be passing CI. Let me know if there's any changes/enhancements you'd like to see.

I think the more idiomatic solution to the SO question would use `map`. Something like: ```dart Future call() async { final userResponse = await _authRepository.getUser(); return userResponse.flatMap((user) { final accessTokenExpiresAtMilliseconds...