kararas_iris

macro

support more than string and int at macro functions route path input arguments: int,uint8,uint16,uint32,int8,int32,int64,slice of strings and string

2018-08-23 17:29:39 +03:00

node

fix https://github.com/kataras/iris/issues/995

2018-05-07 16:49:17 +03:00

api_builder_benchmark_test.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

api_builder.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

fs.go

Add one more browser (and 304 server) cache method using ETag and If-None-Match headers

2018-03-18 11:55:05 +02:00

handler_execution_rules_test.go

Update to version 10.6.5: 1 New Feature And Indonesia Translation | Read HISTORY.md

2018-05-21 07:40:43 +03:00

handler_execution_rules.go

Update to version 10.6.5: 1 New Feature And Indonesia Translation | Read HISTORY.md

2018-05-21 07:40:43 +03:00

handler.go

Update handler.go

2018-04-20 16:56:12 -07:00

macro.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

mime.go

Iris + WebAssemply = = 💓

2018-07-09 09:13:36 +03:00

party.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

path_test.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

path.go

Release of version 10.4.0 - x8 faster embedded file server | Star and Read HISTORY.md

2018-03-14 07:17:35 +02:00

route.go

New ':int64' and ':uint64' route path parameters - and - support the new uint64 for MVC (int64 was already supported there) - and - add ctx.Params().GetUint64 (GetInt64 was already there) - and - make the ':int or :number' to accept negative numbers with no digit limit (at low level) and rename the 'app.Macros().Int.RegisterFunc' to 'Number.RegisterFunc' because number can be any type of number not only standard go type limited - and - add alias for ':boolean' -> ':bool'. Finally, Update the examples but not the version yet, I have to provide a good README table to explain the end-developers how they can benefit by those changes and why the breaking change (which is to accept negative numbers via ':int') is for their own good and how they can make their own macro functions so they do not depend on the Iris builtn macro funcs only. More to come tomorrow, stay tuned

2018-08-23 06:30:12 +03:00

router_handlers_order_test.go

Update to version 10.2.0. Read: https://github.com/kataras/iris/blob/master/HISTORY.md#th-08-february-2018--v1020

2018-02-08 14:04:39 +02:00

router_subdomain_redirect_wrapper.go

…

router_test.go

Add fallback handlers

2018-02-21 12:27:01 +03:00

router_wildcard_root_test.go

…

router.go

remove the complicated fallback handlers, that didn't work and not approve the coblexity addition of the https://github.com/kataras/iris/pull/919 , RouteExists accepts first argument the Context, add new AllowMethods per party and fix cors by https://github.com/iris-contrib/middleware/commit/048e2be034ed172c6754448b8a54a9c55debad46 https://github.com/kataras/iris/issues/922 , rel: https://github.com/iris-contrib/middleware/issues/36 , https://github.com/iris-contrib/middleware/issues/34 , https://github.com/iris-contrib/middleware/issues/32 , https://github.com/iris-contrib/middleware/issues/30 , https://github.com/kataras/iris/pull/909

2018-03-10 14:22:56 +02:00

spa.go

add context#StatusCodeNotSuccessful for customize even the most customized clients that are not compatible with the standards and fix the SPA if static file serve handlers are passed as its AssetHandler as reported at the chat.iris-go.com

2018-01-31 02:35:22 +02:00

status_test.go

…

status.go

add context#StatusCodeNotSuccessful for customize even the most customized clients that are not compatible with the standards and fix the SPA if static file serve handlers are passed as its AssetHandler as reported at the chat.iris-go.com

2018-01-31 02:35:22 +02:00