-
Notifications
You must be signed in to change notification settings - Fork 0
Project cleanup and planning for swift-configuration rewrite #3
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
Conversation
…on from DevFoundation
cee2868 to
c6ee212
Compare
Code Coverage ReportOverall Coverage: 100.00% (3 of 3) DevConfiguration: 100.00% (3 of 3)
|
Plans/Architecture Plan.md
Outdated
| func value(for variable: ConfigVariable<[Bool]>) -> [Bool] | ||
| func value(for variable: ConfigVariable<[String]>) -> [String] | ||
| func value(for variable: ConfigVariable<[Int]>) -> [Int] | ||
| func value(for variable: ConfigVariable<[Double]>) -> [Double] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a subscript version of these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean like _ = configDataSource[.darkMode]?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
…olidate behavior in StructuredConfigReader
|
auto privacy probably needs to cover string arrays as well. |
prachigauriar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, but note that whatever auto privacy setting we have for strings should likely apply to string arrays as well.
Uh oh!
There was an error while loading. Please reload this page.