New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 789667 link

Starred by 1 user
Status: WontFix
Owner:
sjg@chromium.org
Closed: Jan 2018
Cc:
█ bmgordon@chromium.org
la...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature


Show other hotlists

Hotlists containing this issue:
XXX


Sign in to add a comment

libcros_config: support not WARNING on missing property

Project Member Reported by la...@chromium.org, Nov 29 2017 
Some GetString callers (like power_manager) may not want to treat a missing property as exceptional.

This could be a e.g. `bool PropExists(name)` method or another form of GetString that treats missing props differently.

Comment 1 by la...@chromium.org, Nov 29 2017

Cc: la...@chromium.org
I may not get to this.

Comment 2 by sjg@chromium.org, Jan 5 2018

Cc: bmgordon@chromium.org
Status: WontFix (was: Assigned)
I think this is for avoiding logging in that case. Ben has added a mechanism for this, so I think we can close this.

Comment 3 by bmgordon@chromium.org, Jan 5 2018 

https://crrev.com/c/850946 should have turned off the logging in this case, but didn't provide any way for the caller to check if the property exists.

Comment 4 by sjg@chromium.org, Jan 5 2018 

Well GetString() returns false in that case, so I think we already have that.
►

Sign in to add a comment