Daniel Pupius
Daniel Pupius
Primarily targeted at development mode, allow clients to configure a filter for what will get passed through. ```go log.SetHandler(log.FieldFilter("handler", "Login", json.New(os.Stderr))) ```
We experienced a crash today that I'm having trouble diagnosing. The error occurred when calling `logger.Info` inside a goroutine. There were several parallel tasks, all which log when they complete....
One of the errors dispatched by the [oauth2 library](https://github.com/golang/oauth2/blob/master/internal/token.go#L256) contains a `http.Response` which causes the following error: error logging: json: unsupported type: func() (io.ReadCloser, error) This feels like something `WithError(err)`...
If the user clicked 'back' to go back to a cached view you often want to make sure the state is as they left it. Where as if they clicked...
Currently if screens are cache-able they will be kept around forever. It would be worthwhile supporting collection of old screens, so that the cache can be used for quick navigations...
Currently the navigation changes the whole path. It should be possible to white list queryparams that persist across navigations.
A screen may contain multiple tabs that can be navigated to directly. When changing tabs, without doing a full navigation, the history state should be updated accordingly. It should also...
Unless I'm missing something, websocket reverse proxying doesn't work. I haven't looked into what it would require to support this, but it would be pretty nice.
If the specified upstream is down or not responding a fallback would be useful for common error pages. Perhaps ``` /bin/etcdctl set /vulcand/hosts/www.mysite.com/locations/home/fallback myerrorsite ```