Luke Redpath

As a workaround, appending a new line character does seem to solve the problem for me: ```swift extension Snapshotting where Value: Encodable, Format == String { /// A snapshot strategy...

Also seeing this - this is a genuine bug within the library because it is triggering a method from within the view body that has side effects, one of which...

If you don't need backwards compatibility another option would be to see if the built in AsyncImage does what you need and have one less third party dependency in your...

I've been having issues with nanoseconds - its worth noting that if you're seeing specs pass locally but fail on your CI server due to a nanosecond issue, and you're...

Please note that my above recommended fix only worked in Rails 3 by accident and no longer works in Rails 4 as Time.change doesn't support `nsec`. See https://github.com/rails/rails/issues/16392

Potential fix here: https://github.com/danger/danger/compare/master...lukeredpath:patch-1 However, perhaps a better solution would be for the DSL to provide some kind of `debug` function that acts as a proxy to `puts` that won't...

Just chipping in here - another good reason to move all of the reactive extensions into separate repos and libraries is so those of us who do not want to...

You can use the `onFirstResponderStateChanged` property and specifically the `FirstResponderStateChangeHandler.canResignFirstResponder` property for this. ```swift ResponsiveTextField( ... onFirstResponderStateChanged: .init(canResignFirstResponder: { false }) ) ```

@kamcma what do you mean by configured decoder? I don’t see any decoder in the client, except for the one you pass in when calling the particular request overload that...

Hi there, caching is one area where LRResty is lacking at the moment but I'm definitely interested in improving it. Initially I could do more to use the underlying NSURLConnection...