Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Oct 30, 2018. It is now read-only.

Update constraints in SLKTextInputBar on text view content size change#550

Open
algrid wants to merge 1 commit into
slackhq:master from
algrid:fix-543
Open

Update constraints in SLKTextInputBar on text view content size change #550
algrid wants to merge 1 commit into
slackhq:master from
algrid:fix-543

Conversation

@algrid

@algrid algrid commented Nov 6, 2016

Copy link
Copy Markdown
Contributor
  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've been mindful about doing atomic commits, adding documentation to my changes, not refactoring too much.
  • I've a descriptive title and added any useful information for the reviewer. Where appropriate, I've attached a screenshot and/or screencast (gif preferrably).
  • I've written tests to cover the new code and functionality included in this PR.
  • I've read, agree to, and signed the Contributor License Agreement (CLA).

PR Summary

Update SLKTextInputBar subviews constraints on text view content size change (for instance due to font change)

Related Issues

Fixes #543

Comment thread Source/SLKTextInputbar.m
BOOL shouldHide = (self.textView.numberOfLines == 1) || self.editing;
self.charCountLabel.hidden = shouldHide;
}
dispatch_async(dispatch_get_main_queue(), ^{

@dzenbot dzenbot Feb 17, 2017
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm worried that we would be updating the constraints over and over at every content size update. I will need to test this before merging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

1 more reviewer
@dzenbot dzenbot dzenbot left review comments
Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /