代码拉取完成，页面将自动刷新
https://github.com/kataras/iris/issues
https://chat.iris-go.com
https://github.com/kataras/iris/releases
Developers tidak diwajibkan untuk melakukan upgrade apabila mereka tidak membutuhkannya. Anda bisa melakukan upgrade ketika anda sudah siap.
Iris menggunakan fitur vendor directory. Anda mendapatkan build yang benar - benar dapat direproduksi, karena metode ini menjaga terhadap penggantian nama dan penghapusan di upstream.
Cara Upgrade: Bukan command-line anda dan eksekuis perintah ini: go get -u github.com/kataras/iris atau biarkan updater otomatis melakukannya untuk anda.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Indonesian language yet, please refer to the english version of the HISTORY entry instead.
This history entry is not translated yet to the Bahasa Indonesia language yet, please refer to the english version of the HISTORY entry instead.
Every server should be upgraded to this version, it contains an important, but easy, fix for the websocket/Connection#Emit##To.
OnError accepts a func(error) now instead of func(string), as requested at: https://github.com/kataras/iris/issues/987
sessiondb) using the latest features: /sessions/sessiondb/boltdb/database.go, example can be found at /_examples/sessions/database/boltdb/main.go.sessions.Config { Expires } field was 2 *time.Second, it's 45 *time.Minute now.OnDestroy(sid string) on sessions for registering a listener when a session is destroyed with commit: https://github.com/kataras/iris/commit/d17d7fecbe4937476d00af7fda1c138c1ac6f34d.badger and redis as the back-end built'n supported sessions storages, they are enough. Made with commit: https://github.com/kataras/iris/commit/f2c3a5f0cef62099fd4d77c5ccb14f654ddbfb5c relative to many issues that you've requested it.Add new client cache (helpers) middlewares for even faster static file servers. Read more there.
Change the Value<T>Default(<T>, error) to Value<T>Default(key, defaultValue) <T> like ctx.PostValueIntDefault or ctx.Values().GetIntDefault or sessions/session#GetIntDefault or context#URLParamIntDefault.
The proposal was made by @jefurry at https://github.com/kataras/iris/issues/937.
Just remove the second return value from these calls.
Nothing too special or hard to change here, think that in our 100+ _examples we had only two of them.
For example: at _examples/mvc/basic/main.go line 100 the count,_ := c.Session.GetIntDefault("count", 1) becomes now: count := c.Session.GetIntDefault("count", 1).
Remember that if you can't upgrade then just don't, we dont have any security fixes in this release, but at some point you will have to upgrade for your own good, we always add new features that you will love to embrace!
APIBuilder, Party#StaticWeb and APIBuilder, Party#StaticEmbedded wrong strip prefix inside children partiesiris, core/router#StaticEmbeddedHandler and remove the core/router/APIBuilder#StaticEmbeddedHandler, (note the Handler suffix) it's global and has nothing to do with the Party or the APIBuilder
{} (we already escape those contents at the interpreter level but some symbols are still removed by the higher-level api builder) , i.e \\ from the string's macro function regex contents as reported at 927 by commit e85b113476eeefffbc7823297cc63cd152ebddfd
golang.org/x/sys/unix vendorWe've made static files served up to 8 times faster using the new tool, https://github.com/kataras/bindata which is a fork of your beloved go-bindata, some unnecessary things for us were removed there and contains some additions for performance boost.
A new function Party#StaticEmbeddedGzip which has the same input arguments as the Party#StaticEmbedded added. The difference is that the new StaticEmbeddedGzip accepts the GzipAsset and GzipAssetNames from the bindata (go get -u github.com/kataras/bindata/cmd/bindata).
You can still use both bindata and go-bindata tools in the same folder, the first for embedding the rest of the static files (javascript, css, ...) and the second for embedding the templates!
A full example can be found at: _examples/file-server/embedding-gziped-files-into-app/main.go.
Happy Coding!
The only one API Change is the Application/Context/Router#RouteExists, it accepts the Context as its first argument instead of last now.
Fix cors middleware via https://github.com/iris-contrib/middleware/commit/048e2be034ed172c6754448b8a54a9c55debad46, relative issue: https://github.com/kataras/iris/issues/922 (still pending for a verification).
Add Context#NextOr and Context#NextOrNotFound
// NextOr checks if chain has a next handler, if so then it executes it
// otherwise it sets a new chain assigned to this Context based on the given handler(s)
// and executes its first handler.
//
// Returns true if next handler exists and executed, otherwise false.
//
// Note that if no next handler found and handlers are missing then
// it sends a Status Not Found (404) to the client and it stops the execution.
NextOr(handlers ...Handler) bool
// NextOrNotFound checks if chain has a next handler, if so then it executes it
// otherwise it sends a Status Not Found (404) to the client and stops the execution.
//
// Returns true if next handler exists and executed, otherwise false.
NextOrNotFound() bool
Add a new Party#AllowMethods which if called before any Handle, Get, Post... will clone the routes to that methods as well.
Fix trailing slash from POST method request redirection as reported at: https://github.com/kataras/iris/issues/921 via https://github.com/kataras/iris/commit/dc589d9135295b4d080a9a91e942aacbfe5d56c5
Add examples for read using custom decoder per type, read using custom decoder via iris#UnmarshalerFunc and to complete it add an example for the context#ReadXML, you can find them herevia https://github.com/kataras/iris/commit/78cd8e5f677fe3ff2c863c5bea7d1c161bf4c31e.
Add one more example for custom router macro functions, relative to https://github.com/kataras/iris/issues/918, you can find it there, via https://github.com/kataras/iris/commit/a7690c71927cbf3aa876592fab94f04cada91b72
Add wrappers for Pongo's AsValue() and AsSaveValue() by @neenar via PR: https://github.com/kataras/iris/pull/913
Remove unnecessary reflection usage on context#UnmarshalBody via https://github.com/kataras/iris/commit/4b9e41458b62035ea4933789c0a132c3ef2a90cc
Fix subdomains' StaticEmbedded & StaticWeb not found errors, as reported by @speedwheel via facebook page's chat.
A new minor version family because it contains a BREAKING CHANGE and a new Party#Reset function.
As correctly pointed out by @likakuli at https://github.com/kataras/iris/issues/901, the old Done registered
handlers globally instead of party's and its children routes, this was not by accident because Done was introduced
before the UseGlobal idea and it didn't change for the shake of stability. Now it's time to move on, the new Done should be called before the routes that they care about those done handlers and the new DoneGlobal works like the old Done; order doesn't matter and it appends those done handlers
to the current registered routes and the future, globally (to all subdomains, parties every route in the Application).
The routing/writing-a-middleware examples are updated, read those to understand what's going on, although if you used iris before and you know the vocabulary we use you don't have to, the DoneGlobal and Done are clearly separated.
A new Party#Reset() function introduced in order to be able to clear parent's Party's begin and done handlers that are registered via Use and Done at a previous state, nothing crazy about this, it just clears the middleware and doneHandlers of the current Party instance, see core/router#APIBuilder for more.
Just replace all existing .Done( with .DoneGlobal( using a rich code editor (like the VSCode) which supports find and replace all and you're ready to Go:)
New Features:
304 status code, request fires from client to server but server respond with a status code, client is responsible to render the cached, you can find an example here
websocket/Connection#IsJoined(roomName string) new method to check if a user is joined to a room. An un-joined connections cannot send messages, this check is optionally.More:
iris.Cache304app.View example for parsing and writing templates outside of the HTTP (similar to context#View)iris.AutoTLS
Every server should be upgraded to this version, it contains fixes for the tls-sni challenge disabled some days ago by letsencrypt.org which caused almost every https-enabled golang server to be unable to be functional, therefore support for the http-01 challenge type added. Now the server is testing all available letsencrypt challenges.
Read more at:
Not any serious problems were found to be resolved here but one, the first one which is important for devs that used the cache package.
ExecuteWriter -> Load when view#Engine##Reload was true, as requested at https://github.com/kataras/iris/issues/872
golang/crypto to apply the fix about the tls-sni challenge disabled https://github.com/golang/crypto/commit/13931e22f9e72ea58bb73048bc752b48c6d4d4ac (relative to iris.AutoTLS)We must thanks Mrs. Diana for our awesome new logo!
You can contact her for any design-related enquiries or explore and send a direct message via instagram.
At this version we have many internal improvements but just two major changes and one big feature, called hero.
The new version adds 75 plus new commits, the PR is located here read the internal changes if you are developing a web framework based on Iris. Why 9 was skipped? Because.
The new package hero contains features for binding any object or function that handlers may use, these are called dependencies. Hero funcs can also return any type of values, these values will be dispatched to the client.
You may saw binding before but you didn't have code editor's support, with Iris you get truly safe binding thanks to the new
heropackage. It's also fast, near to raw handlers performance because Iris calculates everything before server ran!
Below you will see some screenshots we prepared for you in order to be easier to understand:
hero funcs are very easy to understand and when you start using them you never go back.
Examples:
You have to understand the hero package in order to use the mvc, because mvc uses the hero internally for the controller's methods you use as routes, the same rules applied to those controller's methods of yours as well.
With this version you can register any controller's methods as routes manually, you can get a route based on a method name and change its Name (useful for reverse routing inside templates), you can use any dependencies registered from hero.Register or mvc.New(iris.Party).Register per mvc application or per-controller, you can still use BeginRequest and EndRequest, you can catch BeforeActivation(b mvc.BeforeActivation) to add dependencies per controller and AfterActivation(a mvc.AfterActivation) to make any post-validations, singleton controllers when no dynamic dependencies are used, Websocket controller, as simple as a websocket.Connection dependency and more...
Examples:
If you used MVC before then read very carefully: MVC CONTAINS SOME BREAKING CHANGES BUT YOU CAN DO A LOT MORE AND EVEN FASTER THAN BEFORE
PLEASE READ THE EXAMPLES CAREFULLY, WE'VE MADE THEM FOR YOU
Old examples are here as well. Compare the two different versions of each example to understand what you win if you upgrade now.
Remove the old static variable context.DefaultMaxMemory and replace it with the configuration WithPostMaxMemory.
// WithPostMaxMemory sets the maximum post data size
// that a client can send to the server, this differs
// from the overral request body size which can be modified
// by the `context#SetMaxRequestBodySize` or `iris#LimitRequestBodySize`.
//
// Defaults to 32MB or 32 << 20 if you prefer.
func WithPostMaxMemory(limit int64) Configurator
If you used that old static field you will have to change that single line.
Usage:
import "github.com/kataras/iris"
func main() {
app := iris.New()
// [...]
app.Run(iris.Addr(":8080"), iris.WithPostMaxMemory(10 << 20))
}
New method to upload multiple files, should be used for common upload actions, it's just a helper function.
// UploadFormFiles uploads any received file(s) from the client
// to the system physical location "destDirectory".
//
// The second optional argument "before" gives caller the chance to
// modify the *miltipart.FileHeader before saving to the disk,
// it can be used to change a file's name based on the current request,
// all FileHeader's options can be changed. You can ignore it if
// you don't need to use this capability before saving a file to the disk.
//
// Note that it doesn't check if request body streamed.
//
// Returns the copied length as int64 and
// a not nil error if at least one new file
// can't be created due to the operating system's permissions or
// http.ErrMissingFile if no file received.
//
// If you want to receive & accept files and manage them manually you can use the `context#FormFile`
// instead and create a copy function that suits your needs, the below is for generic usage.
//
// The default form's memory maximum size is 32MB, it can be changed by the
// `iris#WithPostMaxMemory` configurator at main configuration passed on `app.Run`'s second argument.
//
// See `FormFile` to a more controlled to receive a file.
func (ctx *context) UploadFormFiles(
destDirectory string,
before ...func(string, string),
) (int64, error)
Example can be found here.
Just a minor addition, add a second optional variadic argument to the context#View method to accept a single value for template binding.
When you just want one value and not key-value pairs, you used to use an empty string on the ViewData, which is fine, especially if you preload these from a previous handler/middleware in the request handlers chain.
func(ctx iris.Context) {
ctx.ViewData("", myItem{Name: "iris" })
ctx.View("item.html")
}
Same as:
func(ctx iris.Context) {
ctx.View("item.html", myItem{Name: "iris" })
}
Item's name: {{.Name}}
Add a new context#YAML function, it renders a yaml from a structured value.
// YAML marshals the "v" using the yaml marshaler and renders its result to the client.
func YAML(v interface{}) (int, error)
sessions/session#GetString can now return a filled value even if the stored value is a type of integer, just like the memstore, the context's temp store, the context's path parameters and the context's url parameters.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。