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-17 09:57:01 +00:00
Code
Releases
Activity
Files
c746d631d76977ca60c9dfb9ae7d6ff772c9625e
kararas_iris
/
hero
History
Gerasimos (Makis) Maropoulos
bf13f7648a
add vscode extension link and badge | Some internal improvements (not completed yet)
...
Former-commit-id: 9bc94e90a2780ee81f8188509d98063fb3f2924b
2018-01-25 03:16:49 +02:00
..
di
linting, 99% is not fine let's do it 100%
2018-01-04 16:34:04 +02:00
AUTHORS
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
di.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
func_result_test.go
add vscode extension link and badge | Some internal improvements (not completed yet)
2018-01-25 03:16:49 +02:00
func_result.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
handler_test.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
handler.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
hero.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
LICENSE
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
param_test.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
param.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
session.go
split of the mvc and the new hero package is completed, now handlers with input and output binding feature is a different feature than the mvc, however the mvc controller's methods can use the hero dependency injection as before (v10+)
2017-12-25 20:57:04 +02:00