From b06c94565380bc2c3551240125f95dbd7dda6922 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vile=CC=81m=20Kurz?= Date: Fri, 21 Dec 2018 13:32:29 +0100 Subject: [PATCH] 2.1.0 Release --- CHANGELOG.md | 4 ++++ UIViewController-DisplayChild.podspec | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index aec506f..c597129 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,7 @@ +## [2.1.0] +### Added +- `UIStackView` support. You can now use `UIStackView` as a container, and you can insert child's view with animation if you wish. `UIStackView` is a great help, especially if you have multiple childs. You no longer need to set them constraints - `UIStackView` + autolayout will do this for you. + ## [2.0.0] ### Changed - lib uses Swift 4.2 internally diff --git a/UIViewController-DisplayChild.podspec b/UIViewController-DisplayChild.podspec index 79d135e..5fb32e2 100644 --- a/UIViewController-DisplayChild.podspec +++ b/UIViewController-DisplayChild.podspec @@ -1,6 +1,6 @@ Pod::Spec.new do |s| s.name = 'UIViewController-DisplayChild' - s.version = '2.0.0' + s.version = '2.1.0' s.summary = 'UIViewController containment made easy' s.description = <<-DESC The problem: sometimes you need to embed a controller, but it might be embedded already. E.g. you have an empty view, and you do refresh only to get empty view again. If you do not check for its existence, you might end up creating a new instance unneccessarily. This can also have bad side effects when there is some heavier work in viewDidLoad for example.