This website requires JavaScript.
Explore
Help
Sign In
Mirrors
/
kararas_iris
Watch
1
Star
0
Fork
0
You've already forked kararas_iris
mirror of
https://github.com/kataras/iris.git
synced
2025-12-21 11:57:02 +00:00
Code
Releases
Activity
Files
0737c4364c26b51e38c7401331a85b36d5a1cfd4
kararas_iris
/
_examples
/
http_responsewriter
/
herotemplate
/
template
History
Gerasimos (Makis) Maropoulos
07046ab978
formatting
...
Former-commit-id: 037081db5d6d4434e873ca8b75334ee43e046b6a
2019-08-17 10:06:20 +03:00
..
index.html
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
2017-12-25 20:05:32 +02:00
index.html.go
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
2017-12-25 20:05:32 +02:00
user.html
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
2017-12-25 20:05:32 +02:00
user.html.go
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
2017-12-25 20:05:32 +02:00
userlist.html
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
2017-12-25 20:05:32 +02:00
userlist.html.go
formatting
2019-08-17 10:06:20 +03:00
userlistwriter.html
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
2017-12-25 20:05:32 +02:00
userlistwriter.html.go
formatting
2019-08-17 10:06:20 +03:00