New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catalog protocols #2250
Catalog protocols #2250
Conversation
de692e2
to
1ee8a15
Compare
I guess if we can live with the deprecation warnings, this doesn’t actually break anything, right? I’ll test it out for a bit. |
It shouldn't. I just noticed I missed adding |
I like this! Rob - if you're happy with what you've tested so far, I say go ahead with the merge Aside: Wow, after typing "I like this!" I got a kind of spooky feeling... it reminded me of the commit message @tiennou made... 2 and a half years ago: 2719535 every time you force pushed that branch (and it was probably about 20 times!) I got an email who's content was just "@pjrobertson likes those" Scary! |
Between this and the task clean-up, I’m staring at a wall of deprecation warnings we’ve imposed on ourselves. It looks like you’ve taken on a lot of them in #2257. After merging this, I’ll see about getting |
Yeah, right now I'm running *There are some catalog problems because of unfinished librarian-cleanup being in, but it fixes itself after a rescan. The weird thing is that somehow Xcode doesn't show those warnings here yet (they magically appeared when working with a plugin). I'll see what not using my Workspace does btw... |
FYI there's a |
A rejig of #2246, with some tweaks to check_indent because it didn't like documentation comments and staged changes.