You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An accidental space can currently break tag parsing in unfortunate ways. The most insidious example being:
type ServiceConfig struct {
InfluxAddr string `conf:"help:address to influxdb"`
InfluxDB string `conf:"help:influx database to use"`
InfluxUserName string `conf:"help:influxdb username"`
InfluxPassword string `conf:"help:influxdb password, noprint"`
}
Where the config parses just fine, but the space before noprint causes it to be omitted, meaning INFLUX_PASSWORD will appear in the result of conf.String() No bueno.
The text was updated successfully, but these errors were encountered:
flowchartsman
changed the title
Better tag parsing for odd spaces
Better tag parsing for things like erroneous spaces
Mar 11, 2019
An accidental space can currently break tag parsing in unfortunate ways. The most insidious example being:
Where the config parses just fine, but the space before
noprint
causes it to be omitted, meaningINFLUX_PASSWORD
will appear in the result ofconf.String()
No bueno.The text was updated successfully, but these errors were encountered: