New Issue Checklist

• [x ] I have read and understood the CONTRIBUTING guide
• [x ] I have read the Documentation
• [ x] I have searched for a similar issue in the project and found none

Issue Info

Info

Some files in the repository are missing newlines at the very end, as pointed out by @nrbrook in #1026

Classes/CocoaLumberjack.h was specifically mentioned, but there could be other files that are missing this as well.

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

In several WWDC talks, Apple suggests to set the Input and Output files in all run script phases, so the build system can choose to skip a run script phase if nothing changed, improving incremental build time.

How could we improve R.swift‘s behavior here?

Note that I did not yet check if wildcards were allowed in the Input Files field. Or if we could somehow leverage the new File List field.

log.debug("A tagged log message", userInfo: Dev.dave | Tag.sensitive)

That's somehow will confuse the user who only advantages one kind of Tag.
Then I suggest appending one demo code as below for that scenario.
log.debug("A tagged log message", userInfo: Tag.sensitive.dictionary)

Lots of new error codes were added during the localization work. The website docs need to be updated with these new error codes.

Ideas:

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

Hey there.
Thanks for the article https://nshipster.com/secrets/, I've had similar thoughts that client cannot safely store the secrets.

One possible issue I noticed (or maybe I'm just not knowledgable enough about the matter) is that Matt mentioned this in the article:

Your mission: Transfer a payload from the server and store it in the Secure Enclave without an attacker compromising it

Hi Dan 👋 Thanks a lot for the library, I’m using it in a modern Mac app and cannot be happier.

I’m curious about callbacks when the procedure is cancelled or finished with an error. So what is the best practice to handle all events once the job is done?

I always did something like this (os_log is a placeholder, treat it as UI updates):

let job = MyAsyncProcedure()
job.addDidC

Can anyone help me out with this error? I don't know what to change my bundle identifier to for this to work? @gabrieloc

Any plan to add pagination to the post list?