Skip to content
This repository has been archived by the owner on Feb 28, 2019. It is now read-only.

Fixes passing nil request into handler #32

Merged
merged 4 commits into from
Nov 10, 2017
Merged

Conversation

m-sandusky
Copy link
Contributor

Fixes issue where nil was passed instead of the request (probably should never do that :) )

@coveralls
Copy link

coveralls commented Nov 9, 2017

Coverage Status

Coverage remained the same at 45.737% when pulling b64bbe9 on fix-nil-pointer into 52edc60 on master.

@@ -194,8 +194,8 @@ func (s *service) sendResponse(w http.ResponseWriter, statusCode int, data inter
return writeAPIResponse(w, http.StatusInternalServerError, "could not create response object")
}

func (s *service) fetchNamespaces(w http.ResponseWriter, _ *http.Request) error {
data, err := handleRoute(fetchNamespaces, s, nil, "")
func (s *service) fetchNamespaces(w http.ResponseWriter, r *http.Request) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mind adding a regression test for it as well?

@coveralls
Copy link

coveralls commented Nov 10, 2017

Coverage Status

Coverage increased (+0.2%) to 45.957% when pulling 0880c87 on fix-nil-pointer into 52edc60 on master.

@coveralls
Copy link

coveralls commented Nov 10, 2017

Coverage Status

Coverage increased (+0.2%) to 45.957% when pulling 5589250 on fix-nil-pointer into 52edc60 on master.

@coveralls
Copy link

coveralls commented Nov 10, 2017

Coverage Status

Coverage increased (+0.2%) to 45.957% when pulling 4f17124 on fix-nil-pointer into 52edc60 on master.

Copy link
Contributor

@xichen2020 xichen2020 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@m-sandusky m-sandusky merged commit 18fdaea into master Nov 10, 2017
@m-sandusky m-sandusky deleted the fix-nil-pointer branch November 10, 2017 22:29
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants