JP Simard

Typed declarations

1

Move away from stringly-typed dictionaries. Previous conversation in #87.

Always link to Foundation

4

Otherwise, code that compiles and uses Foundation symbols but without `import Foundation` in the file would generate bad USRs (`s:F10RealmSwift12migrateRealmERR` vs `s:F10RealmSwift12migrateRealmFTSS13encryptionKeyGSqCSo6NSData__GSqCSo7NSError_`.

Render parameters and return discussion in jazzy

2

Since these are now just markdown list items, this should be _relatively_ easy. However, I had a really hard time figuring out the best way to do so in redcarpet,...

This will make passing UI events much more modular and make supporting non-command-line tools much easier.

First off, thank you very much for this gem. It's been powering a Swift & Objective-C documentation generator for years, and I'm very grateful! 🙏 We recently ran into a...

At the moment, we just refresh all windows every time any of their Realms is updated. See https://github.com/realm/realm-browser-osx/pull/215#issuecomment-251753217

Inverse relationships aren't persisted in Realm files, but rather set up at runtime. Some users have requested the ability to visualize those in the browser nonetheless. One way this could...

By parsing xcodebuild output, we should be able to detect which swift files are compiled for the module being tested. SourceKitten does this. This would avoid the basic `file.endswith('.swift') and...

Tests are currently run twice: both before and after setting breakpoints. We could perhaps use xcodebuild's `-dry-run` argument, or a test scheme could be passed in instead of xcodebuild parameters,...