iOS dev by day and indie iOS dev by night. Working on @warganizer, @jinks_app and https://nitter.gq/t.co/EC43aKXort
Berlin, Deutschland
Joined February 2014
- Tweets4.3K
- Following338
- Followers1.5K
- Likes17.1K
Pinned Tweet
I got into SwiftUI some time ago. After sprinkling a few files into my projects, I decided to take a look at a full rewrite.
That app is not even close to be released, but some packages are!
Let me introduce the SNAP package suite: github.com/simonnickel/snap-…
🧵 for details …
Does anyone have experience with hacked Instagram accounts?
Somehow someone managed to change the email address of my wifes account. Without her getting an email to confirm the new email.
The support only references this email to revert the email change.
It’s like telling kids not to go to school because a calculator can do the math for you.
It’s stupid.
This Post is from an account that no longer exists. Learn more
Feels like Apple is in final Feedback mode before WWDC.
Just got a response to github.com/simonnickel/FB133…… with an updated example code to show what I did wrong 🤯👏
The proposed solution still does not work on iOS though 🙄
After a few month into the big rewrite of Figure Case it feels weird to have nothing to release for a while.
So I just created a tiny update 🤷♂️
… waiting for review actually feels good 😅
1. SnapCore - A collection of useful helper implementations, common extensions, convenience definitions and workarounds.
github.com/simonnickel/snap-…
When I run into SwiftUI workarounds, I try to make them reusable.
Contains a conditional ViewModifier, can’t do SwiftUI without it!
5. SnapAppTemplate
github.com/simonnickel/snap-…
Where all packages come together:
1.Infrastructure with the packages ready to go.
2.Define a navigation hierarchy for the app.
3.SnapMatchingNavigation
4.Settings screen with some theme configuration options.
6. SnapSwiftData
github.com/simonnickel/snap-…
A bonus package to improve interoperability between SwiftData and CoreData. It provides SwiftData with access to CoreData objects and Persistent History Tracking.
Are there any Swift Macro experts around?
Seems like a steep learning curve and I am not sure if I should even begin to look into it deeper.
Is it possible to get the name of the attribute the macro is attached to?
Simon Nickel retweeted
Use AsyncStream.makeStream instead :) donnywals.com/building-an-as…
AsyncStream is such a weird API. Or am I just holding it wrong?
I need the continuation to send values to, but there is no good way to keep the continuation.
That’s the best I could come up with. I don't want it to be optional, but I have to.
ALT public let remoteChangeStream: AsyncStream<X> private let continuation: AsyncStream<X>.Continuation? public init() { var tempContinuation: AsyncStream<PersistentIdentifier>.Continuation? self.remoteChangeStream = AsyncStream { (continuation: AsyncStream<X>.Continuation) -> Void in tempContinuation = continuation } self.continuation = tempContinuation }
Simon Nickel retweeted
I'm not very active here anymore, but I made something: swiftuifieldguide.com
