Skip to content

Tags: lukeredpath/swift-responsive-textfield

Tags

0.11.0

Toggle 0.11.0's commit message

Verified

This commit was signed with the committer’s verified signature. The key has expired.
lukeredpath Luke Redpath
fix: Bump combine-schedulers dependency

0.10.1

Toggle 0.10.1's commit message

Verified

This tag was signed with the committer’s verified signature. The key has expired.
lukeredpath Luke Redpath
release: v0.10.1

0.10.0

Toggle 0.10.0's commit message

Verified

This tag was signed with the committer’s verified signature. The key has expired.
lukeredpath Luke Redpath
release: v0.10.0

0.9.0

Toggle 0.9.0's commit message

Verified

This tag was signed with the committer’s verified signature. The key has expired.
lukeredpath Luke Redpath
release 0.9.0

0.8.1

Toggle 0.8.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix: Updating textColor and textAlignment when state changes (#15)

0.8.0

Toggle 0.8.0's commit message

Verified

This tag was signed with the committer’s verified signature.
lukeredpath Luke Redpath
Bump dependencies.

0.7.0

Toggle 0.7.0's commit message

Verified

This commit was signed with the committer’s verified signature.
lukeredpath Luke Redpath
Update CHANGELOG

0.6.0

Toggle 0.6.0's commit message

Verified

This commit was signed with the committer’s verified signature.
lukeredpath Luke Redpath
Fixes attribute graph cycle errors in Xcode 13.

I'd hope to avoid this brute-force approach but this seems to be the
only way to ensure there aren't nested view updates triggered by
changing the textfield responder state.

0.5.2

Toggle 0.5.2's commit message
Wrap calls to super in an explicit closure.

For some reason, passing the super implementation in a point-free
style here is causing malformed coverage data in an app that uses
this library - I have no idea why this is occurring but this does
seem to fix the problem.

🤷🏻‍♂️

0.5.1

Toggle 0.5.1's commit message
Fix bug with standard edit action handling where original might not

get called.

The logic is supposed to be that if a custom override is provided
and it returns true, the original should be called, but if no override
is provided then the original should be called.

The previous implementation was calling the original using optional
chaining which meant the original would not be called if the override
was nil.

This change fixes that bug and also refactors out the duplicated
logic into a more general function.