Choly.ca Website Review

NOTE: Replace thing with your own repo name in the examples.. 2. CLONE ONE OF THE EXISTING REPOSITORIES TO A TEMPORARY LOCATION.     if err != nil {         http.Error(w, err.Error(), 500) Ideally, I could just return an error from the handler. Let’s create a type to let that happen.         http.Error(w, err.Error(), 500)     } Here’s the previous code refactored to use the new handler. Better, but what if we want to control the error status code? There could be a special error type that MyHandlerFunc checks for. func (e MyError) Error() string {     return fmt.Sprintf(%d: %s, e.Code, e.Text)         if e, ok := err.(MyError); ok {             http.Error(w, e.Text, e.Code)         } else {             http.Error(w, err.Error(), 500)     if err != nil {         return MyError{Code: 400, Text: SomeError} This is alright, but we can do better. Let’s change the handler function signature so that it returns another http.Handler. This will give the returned object complete control over how it’s handled. With this in place, we can implement all kinds of interesting helpers.         w.WriteHeader(code)         h.ServeHTTP(w, r)         http.Error(w, err.Error(), code)     })     if err != nil {         return Error(err, 500)     case http.MethodGet:         return GetThing(w, r)     case http.MethodDelete:         return DeleteThing(w, r)         return WithStatus(404, Text(not found))     } I’ve been trying to find an elegant way of dealing with events in AngularJS recently. If you’re not fa*miliar with Angular, that’s function MyController($rootScope) {   $rootScope.$on('event1', () => { There’s an issue with this code. It doesn’t unbind the listener when the controller (or its scope) is destroyed. Let’s take care of