| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Found that LPLinkMetadata + NSItemProvider can actually use UIImage. I
think this is better now since not using a bundle load and can use
assets.
|
|
|
|
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.
|
|
Note that URLSession async only works >=iOS 15. I changed the target for
now, but may mess with continuations.
|
|
|
|
|
|
This is admittedly pretty hard for me to wrap my head around, and I'm
not even using background threading explicitly yet. Will improve.
|
|
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
|
|
Just an idea I had, since it was quite messy that a TableViewController
was handling all that. Instead now it should be reusable through the
ForayCoordinator itself, which means e.g. on details screen, we can show
the loading overlay.
|
|
Resources:
- https://www.hackingwithswift.com/articles/71/how-to-use-the-coordinator-pattern-in-ios-apps
|
|
|
|
It isn't much so far, as it is just effectively the API retrieval
function extracted from the TableViewController. But this should also
allow other VCs to get from API too if required :^)
|
|
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.
|
|
Cell no longer uses prototypes as registered in the Storyboard. Instead
is a custom class inheriting the UITableViewCell and is manually
registered by the VC.
This is a first step towards reimplementing the prototype cells. Only
has one label at the moment.
|
|
Was thinking of using CocoaPods as that's what is in use, but either way
looked decently straightforward. Decided to start with whatever was
already built in and no extra software.
Note: it was File > Add Packages > put git link in top right. References
I saw seemed to say File > Swift Packages and I couldn't find it. Also
some other docs had older screenshots, I presume it's pre-Xcode-13 being
slightly different.
References:
- https://developer.apple.com/documentation/swift_packages/adding_package_dependencies_to_your_app
- https://www.raywenderlich.com/7242045-swift-package-manager-for-ios
- https://snapkit.io/docs/
|
|
Luckily it was only one file
|
|
Resources:
- https://guides.codepath.com/ios/Using-UITableView (was a bit dated)
|
|
Forgot to commit after finishing just the using array data bit. So committing with the custom cells done.
https://www.ralfebert.com/ios-examples/uikit/uitableviewcontroller/
|
