| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Wow, I didn't know `if let` was a thing back then, haha. Also made
UIImage a bit safer in case asset is missing by unwrapping in one common
place.
|
|
|
|
|
|
In preparation for presenters to come in largely, lots of files starting
to go everywhere...
|
|
Also fixed the scrollview margins while I was at it - it looked weird
being so inside
|
|
Didn't constrain details label to the bottom of the content container,
so scroll view didn't pick up on it (test with large font on a smaller
viewport phone).
|
|
Resources:
- https://www.hackingwithswift.com/articles/71/how-to-use-the-coordinator-pattern-in-ios-apps
|
|
Would make more sense as more lines get added in (especially if ui
elements programatically), as well as since horizontal layout is allowed
if the screen is small you can scroll
|
|
Not sure if this is the right move, but it felt extraneous to have a
whole UIView to itself for now. Instead just have it right inside the
VC.
Probably a step in the wrong direction though, but will need to review.
|
|
|
|
Note - I had to fo into the Target settings -> Info -> Custom iOS Target
Properties -> adjust the Application Scene Manifest there.
Resources:
- https://ioscoachfrank.com/remove-main-storyboard.html
- https://stackoverflow.com/questions/25167458/changing-navigation-title-programmatically
|
|
Using SnapKit and some experimentation around the VC. Next step is to
change segue and then maybe get rid of storyboard all together.
|
|
Makes it clear which parts are tightly coupled. I want to learn how to
make this more generic so I can try hooking into other APIs easily
(which make require different destructuring of JSON).
|
|
|
|
Resources:
- https://guides.codepath.com/ios/Using-UITableView (was a bit dated)
|
