Reset unintended CodingGuidelines changes

This commit is contained in:
Mihael Cholakov 2020-01-07 09:51:09 +02:00
parent 593a802d79
commit af5fd716fd
1 changed files with 3 additions and 3 deletions

View File

@ -36,8 +36,6 @@ Functions should tend to be small. One-liners are a-okay, especially when the fu
We mostly avoid Swift generics, since generics is an advanced feature that can be relatively hard to understand. We *do* use them, though, when appropriate.
Its totally okay to use the magic `error` variable when catching errors. In accessors, use of the magic `oldValue` and `newValue` is expected when you need the old or new value.
We use assertions and preconditions (assertions are hit only when running a debug build; preconditions will crash a release build). We also allow force-unwrapping of optionals as a shorthand for a precondition failure, though these should be used sparingly.
Extensions, including private extensions, are used — though we take care not to extend Foundation and AppKit objects too much, lest we end up with our own Cocoa dialect.
@ -104,7 +102,7 @@ Dont fight the built-in frameworks and dont try to hide them. Lets not
NetNewsWire is layered into frameworks. Theres an app level and a bunch of frameworks below that. Each framework has its own reason for being. Dependencies between frameworks should be as minimal as possible, but those dependencies do exist.
Some frameworks are not permitted to add dependencies, and should be treated as at the bottom of the cake: RSCore, RSWeb, RSDatabase, RSParser, and RSTree. This simplifies things for us, and makes it easier for us and other people to use these frameworks in other apps.
Some frameworks are not permitted to add dependencies, and should be treated as at the bottom of the cake: RSCore, RSWeb, RSDatabase, RSParser, RSTree, and DB5. This simplifies things for us, and makes it easier for us and other people to use these frameworks in other apps.
### User Interface
@ -112,6 +110,8 @@ Stick to stock elements, since this tends to eliminate bugs and future churn. Th
Storyboards are preferred to xibs — except when the problem is xib-sized.
Use DB5 where parameters (sizes, colors, etc.) are needed.
Auto layout is used everywhere except in table and outline view cells, where performance is critical.
Stack views are not allowed in table and outline view cells, but they can be useful elsewhere. However, care must be taken that performance (of window resizing, for instance) is not affected. When it is, dont use a stack view.