Releases: wrabit/django-cotton
v0.9.23
What's Changed
An issue caused a discovery that tags were being mutated if DTL syntax was against an opening tag name i.e.
<li{% expr %}>..</li>
Which after processing resulted in:
<li{% expr %}>..</li{% expr %}>
We solved it by better handling of white space when we match and replace the DTL expressions.
Full Changelog: v.0.9.22...v0.9.23
v0.9.21
v.0.9.22
v0.9.20
What's Changed
Default charset when processing template files should be utf-8 or as defined in the the loader settings. This was being skipped. Related to an issue from @zagro-dev.
- fixed tabbed component on docs home by @wrabit in #58
- improved some coherence in component and slot by @wrabit in #59
Full Changelog: v0.9.19...v0.9.20
v0.9.19
What's Changed
@pedroven identified an issue where the loader was not allowing us to use Django template expressions to govern whole attributes inside html elements. This was due to the compilation where BS4 cleanses HTML removing duplicate attributes adhering to html spec:
There must never be two or more attributes on the same start tag whose names are an ASCII case-insensitive match for each other.
Since our target is not HTML, but Django Template Language, this behaviour is not desirable, we now manage this in the Cotton Compiler.
Full Changelog: v0.9.18...v0.9.19
v0.9.18
v0.9.17
v0.9.16
What's Changed
Cotton components are now cached whilst in production / DEBUG = False
.
- The cache type is LRU with a record count of 1024 which will be cleared on app restart
- Future refinement needed to optimise the responsibility of caching in the loader
- Planned improvement of hybrid caching during development
Full Changelog: v0.9.15...v0.9.16
v0.9.15
What's Changed
When we want to explicitly access attribute as a var which has '-' hyphens, it will be accessible by the snake case form. i.e.
<c-component x-data="{}" />
{{ x_data }}
Note: This does not affect attribute names within {{ attrs }}
where any hyphenated name will stay hyphenated.
Full Changelog: v0.9.14...v0.9.15
v0.9.14
What's Changed
The vars frame is now only used when we have specified a <c-vars />
tag in a compoent. From benchmarks, there's a ~15% performance increase:
10k components rendering:
Before:
1.71s
After:
1.39s
Full Changelog: v0.9.13...v0.9.14