go-packages/iris
1
0
Fork 0
mirror of https://github.com/kataras/iris.git synced 2025-01-23 18:51:03 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

_future

Browse Source 
Former-commit-id: 25d74bdc601e9c8896b2086566b81196978269f3
This commit is contained in:
Gerasimos (Makis) Maropoulos 2017-03-19 04:00:42 +02:00
parent 55e1e79816
commit 069b81c377
2 changed files with 13 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
_future/README.md
View File

@ -3,18 +3,9 @@
<img width="570" src="https://github.com/iris-contrib/website/raw/gh-pages/assets/simplicity_random_image_but_suitable_because_iris_has_the_same_slogan.gif" alt="Simplicity Equals Productivity" />
</a>
<br/>
<a href="http://iris-go.com/">Simplicity Equals Productivity</a>
</p>
# Future | Inspiration for new developers.
## _future
This folder contains features that are marked as 'work-in-progress', they can take a long to be fully implemented and adopted to the Iris framework itself, even months.
@ -22,6 +13,7 @@ Some people may find that bad idea, for many and different reasons, to upload th
But I think that it is a good place for new developers to view and track how a feature is being implemented step-by-step. How I develop Iris step-by-step.
# Inspiration for new Iris Developers.
I have collected some tips for you!
@ -36,3 +28,8 @@ I have collected some tips for you!
And never forget, **If I can do it, so can you!**
# Any brilliant ideas of yours?
I'll be glad to talk with you about your awesome feature requests,
open a new discussion [there](http://support.iris-go.com), you will be heard!

11
_future/macros.go
View File

@ -7,16 +7,17 @@ Here I should think a way to link the framework and user-defined macros
with their one-by-one(?) custom function(s) and all these with one or more PathTmpls or visa-versa
These should be linked at .Boot time, so before the server starts.
Tthe work I have done so far it should be resulted in a single middleware
The work I have done so far it should be resulted in a single middleware
which will be prepended to the zero position, so no performance cost when no new features are used.
The performance should be the same as now if the path doesn't contains
any macros:
macro = /api/users/{id:int} or /api/users/{id:int range(1,100) !404}
no macro = /api/users/id}).
no macro = /api/users/id
I should add a good detailed examples on how the user can override or add his/her
own macros and optional functions can be followed (i.e, func = range(1,5)).
I should add good detailed examples on how a user can override or add his/her
own macros and any optional function(s) can be followed (func = range(1,5)).
Of course no breaking-changes to the user's workflow(I should not and not need to touch the existing router adaptors).
Of course no breaking-changes to the user's workflow.
I should not and not need to touch the existing router adaptors.
*/