Releases: indigo-web/indigo
Releases · indigo-web/indigo
v0.6.3
v0.6.2
Changelog:
- Minor updates: fixed bugged internal function. This did not cause anything bad internally, but in future possibly could
Full Changelog: v0.6.1...v0.6.2
v0.6.1
v0.6.0
Changelog:
- Updates of request object: now transfer encoding values are contained in a separated struct (breaks backward capability)
- Heavily optimized the process of headers storing - now the access is linear, but appending is constant. So the performance in worst cases is still the same as was before. The only penalty is that fetching all the headers keys is pretty expensive (and causing at least one extra allocation per once, if a desired key is presented)
- Other internals minor updates
What's Changed
Full Changelog: v0.5.1...v0.6.0
v0.5.1
v0.5.0
v0.4.0
What's Changed
- New middleware, performance improvements, bug fixes by @fakefloordiv in #74
- Fixed installing troubles by @fakefloordiv in #75
Note: I recently found out that switching to v1 was a mistake. Package is still very young, and changing all over codebase, and many changes that are bringing some good features aren't compatible with an actual API. After I tried to make the process of responding with a file a bit less crutchy, I understood one thing - this is gonna be a shitcode. On the other hand, I could break a backward capability, but that would be a third major version since there is only 2.3.1 on v2 branch. So as that change wouldn't be that wide, I decided that from 2 evils I'm not gonna choose any of those. Just roll version back to unstable (v0). Nobody anyway uses it