Using MusicKit how can I get a tracks release year?
As far as I can tell releaseDate is always nil, do I need to make a further request to populate this property?
A track always contains a releaseYear property so far as I can tell, but this is not exposed, as in I can't do myTrack.releaseYear
This is for a personal project, so I don't mind a hacky solution if that's what it takes. #swift#musickit
It seems I can get this data easily using the JSON API, just not with the Swift MusicKit. Also it seems the IDs that the Swift library uses are different to the ones the API uses, meaning I have to re-write everything. So... fun.
On the off chance this is useful to anyone else - the ID I had is returned from a playlist, meaning its an ID for a track in my library, not for a track in the Apple Music catalog. So although the data is the same, you have to make a request to the library not the catalog.
I think I now have this sorted with minimal changes needed to my existing code. Although it did take a lot of fiddling around.
I tested the advice that marking classes in #swift as final improves build times. I generated 2 swift files that each have 1000 (trivial) classes: one with each marked as final, the other without. I built each file 10 times, recording the build time for that file.
Marking classes as final does improve build times. By about 7%. The difference is just outside 1 standard deviation, so I think it’s statistically significant. But I’m not a trained statistician.
App Review rejected my macOS menu bar app, Done, because the “app menu is missing the required Quit option.“
However, the app allows a quit operation by right clicking the menu bar app icon and choosing quit. Do menu bar apps usually support other methods to quit? Is it possible they didn’t try this?
If you are looking for a weather app that is simple and does not track your location, try Ducky Weather! One thing I have found in our research group is that the most popular free weather applications send your location to trackers and I wanted to create an app that does not do that. Because it uses NWS data, it is only available in the US.
More features to come but suggestions are welcome!
The main obstacle to make this happen was to trick myself into buying a Windows machine by rekindling my love for video games via a very delightful detour called the #GamePortingToolkit.
If I want to use String(localized:) to localize a variable, is this the best way? I can’t put it in directly like I used to with NSLocalizedString. In this case, the variable comes from Core Data, otherwise I could probably declare it directly as LocalizedStringResource. #Swift#SwiftUI#UIKit#Localization
I have added a shortcut for refreshing packages. Next step, I'll see if I can add a separate button to Cork itself for only refreshing packages without updating them!
(also, does anyone know why Shortcuts is showing the key for each LocalizedStringResource instead of the actual string? 🤔 see pic #2 for code)
“With the increased limit of the acceptance queue, and a patched version of wrk, we can now conclude that swift is a good competitor speed-wise as a web application server.
Memory wise it blows all the other technologies away, using only 2.5% of the amount of memory that the java implementation needs, and 10% of node-js.”
@finestructure always seemed to me to be a weird benchmark where the endpoint has a heavy CPU load. Not very typical of a standard server. Some interesting discussion though. Not sure the decision to accept more connections when server is overloaded is very clever though.
Swift/SwiftUI Question: App Store Connect API provides a gzip when the response is successful for a particular endpoint I am accessing.
How do I take this gzip and save the contents of it to a files app / sandbox directory / swift data, so that I can read it and view the contents? From what I understand, gzip is similar to a zip file?
So far my attempts to save it to files to read the contents have failed. It says “Inappropriate file type or format”.
How would you go about implementing a popup search menu like this? :think_bread:
Suppose I have a NSSearchField and want to make such popup menu to let the user choose some details about their search - for example, if they want to search by a package's name or description.
Or would there be a more appropriate, and completely different, solution? What do you think?
@Bryan The main problem is showing that menu with the options. I'm not sure how to do that in SwiftUI, but there might be a way in AppKit that I'm not aware of since I'm using NSSearchField
so i've been working on combining overloaded methods into a single “overload group" in curation and navigation. the work is currently landed on main and release/6.0, but right now it will just list all the overloaded symbol declarations on the page without showing you what's actually distinct between them
It will be my birthday soon on June 1st, and to celebrate, I’ll be offering a super special discount on Cork! 🎉
Starting on June 1st until June 8th, Cork will be discounted 60 percent! Yes, SIXTY, the largest discount ever.
I’ll be sharing the discount code later, so be sure to keep an eye on my profile or @CorkApp (or even follow me if you want to, I’d really appreciate that!)
From 2 days I've been trying to animate icons in a small utility app I made with MenuBarExtra. I can’t seem to figure out how Paste app did this animation, that goes off every time the user copies something. Anyone? Any idea?
I'm looking for some volunteers to test a new Cork version. There's one huge bug that needed to be fixed before the next version is released. Are you up for it?
I'm specifically looking for people with a lot of installed Homebrew packages.
I was invited to Vincent Pradeille's YouTube channel to share some advanced Swift tips and insights from my new book "Swift Gems" 📘✨ The video is now live, check it out: https://www.youtube.com/watch?v=557nJYhPb7Y
It checks if a specified URL is a symlink, which works fine. But I'm having problems actually resolving the symlink using resolvingSymlinksInPath()
In the testing part at the bottom, I'm getting this: Resolved symlink result: file:///Users/david/Developer/Testing/folderThatIsSymlink | expected /Users/david/Developer/Testing/folderThatIsSymlinkTarget
Are there any #Swift API design best practices about error handling?
So far, I sketched everything with Result<Value,Error> so I get typed errors.
But both stack unwinding and the lack of ceremony of throws is appealing, too. API consumers probably don't need fine grained detail which of the 20 error cases occurred.
@ctietze I think in practice, there are very few reasons why callers should care about error types. The binary worked/failed is so applicable to so many situations, and I think you have to have a very compelling reason to not use it.
