iris/_examples/hero/overview/web/middleware/basicauth.go

// file: web/middleware/basicauth.go

package middleware

import "github.com/kataras/iris/v12/middleware/basicauth"

// BasicAuth middleware sample.
var BasicAuth = basicauth.New(basicauth.Config{
	Users: map[string]string{
		"admin": "password",
	},
})
create a new package, name it as hero, I was thinking super or superb but hero is better name for what it does - the goal is to split the new 'mvc handlers' from the mvc system because they are not the same, users should know that they can use these type of rich binded handlers without controllers as well, like a normal handler and that I implemented here, the old files exist on the mvc package but will be removed at the next commit, I have to decide if we want type aliases for Result or no Former-commit-id: cb775edc72bedc88aeab4c5a6de6bfc6bd56fae2 2017-12-25 19:05:32 +01:00			`// file: web/middleware/basicauth.go`

			`package middleware`

obey the vote of @1370 (77-111 at this point) - add import suffix on iris repository We have to do the same on iris-contrib/examples, iris-contrib/middleware and e.t.c. Former-commit-id: 0860688158f374bc137bc934b81b26dcd0e10964 2019-10-25 00:27:02 +02:00			`import "github.com/kataras/iris/v12/middleware/basicauth"`
create a new package, name it as hero, I was thinking super or superb but hero is better name for what it does - the goal is to split the new 'mvc handlers' from the mvc system because they are not the same, users should know that they can use these type of rich binded handlers without controllers as well, like a normal handler and that I implemented here, the old files exist on the mvc package but will be removed at the next commit, I have to decide if we want type aliases for Result or no Former-commit-id: cb775edc72bedc88aeab4c5a6de6bfc6bd56fae2 2017-12-25 19:05:32 +01:00
			`// BasicAuth middleware sample.`
			`var BasicAuth = basicauth.New(basicauth.Config{`
			`Users: map[string]string{`
			`"admin": "password",`
			`},`
			`})`