This is not an issue but an observation. I no longer use storyboards for my view. Today I faced an issue with Skeletonview when I added it to my UITableViewCell, animations, frames everything was working wrong... did a lot of permutation combinations turning the properties on and off. Finally found that when you add elements in UITableViewCell you should add it to contentView and not to th

While generating docs for the v5.2, I noticed our doc coverage dropped to 99% due to a forgotten doc here. and was wondering if it is a good idea to add a CI step to make sure any newly introduced code is properly documented

I just wanted to note that I was reading the documentation for 7.1 (thanks for that by the way, it's a great update), and I wasn't sure what was meant by Transformable and it's new version Field.Coded. I thought that was odd since I've read the README documentation dozens of times by now, so I searched through it and couldn't find anything. Could you add documentation about what Field.Coded

Ideas:

• Set a minimum dimension for images.
• Find a way to detect dimensions before downloading the image.

Currently, the framework is lagging unit testing. Add some unit test.

Hello,

I run it on simulator and I don't know if it's a bug but you can't scroll to see all screen on AppleTV, I think it's because images are not focusable..

When we can eventually target macOS 10.15 in the far future, we could use NSToolbarItemGroup instead of placing a segmented control in the toolbar.

https://developer.apple.com/documentation/appkit/nstoolbaritemgroup/selectionmode/selectone
https://developer.apple.com/documentation/appkit/nstoolbaritem/3237224-isbordered
https://developer.apple.com/documentation/appkit/nstoolbaritem/3237225-

Help welcome to add more tests :)