Skip to content

Commit 4882e1f

Browse files
committed
Update gems
1 parent 993e9bc commit 4882e1f

File tree

3 files changed

+3
-2
lines changed

3 files changed

+3
-2
lines changed

.ruby-version

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
ruby-2.7.0

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
## [1.9.0](https://github.com/layoutBox/PinLayout/releases/tag/1.9.0)
1111
Released on 2019-10-03
1212

13-
#### Automatic Sizing (UIView conly)
13+
#### Automatic Sizing (UIView only)
1414

1515
* By calling `autoSizeThatFits` with the given available size and a layout closure, any layouting performed by PinLayout in that closure will be computed without affecting any subview's `frame` in the view hierarchy. On the other hand, any non PinLayout related code will also be executed. For that reason, it is really important to separate your layout code in it's own function to avoid any side effect during sizing, like setting the scroll view's content size in the above exemple or perhaps assigning `itemSize` in a collection view layout. That kind of code that depends on the layout should only be executed when `layoutSubviews()` is called as part of a normal layout pass. The resulting size also takes into account the margins applied on subviews, even on the bottom and trailing sides. Automatic sizing makes it really easy to write your layout logic once and add proper sizing behavior with virtually no additional effort. See https://github.com/layoutBox/PinLayout#automatic_sizing for more documentation.
1616
* Added by [Antoine Lamy](https://github.com/antoinelamy) in Pull Request [#216](https://github.com/layoutBox/PinLayout/pull/216)

Gemfile.lock

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,4 +105,4 @@ DEPENDENCIES
105105
xcpretty-travis-formatter
106106

107107
BUNDLED WITH
108-
1.17.1
108+
2.1.2

0 commit comments

Comments
 (0)