Releases: gurgunday/ghtml
v3.0.8
Issue: In previous versions, we used == null to check if values were null or undefined. However, this check inadvertently included document.all due to its unique behavior of being nullish in equality checks despite being an object. This was causing inconsistencies in certain browser environments where document.all is used as a legacy feature.
Fix: The equality check has been updated to use the nullish coalescing operator ??. This ensures that only null or undefined values are filtered out.
Full Changelog: v3.0.7...v3.0.8
v3.0.7
Full Changelog: v3.0.6...v3.0.7
v3.0.6
Full Changelog: v3.0.5...v3.0.6
v3.0.5
Contributors
Assets 2
v3.0.4
Contributors
Assets 2
v3.0.3
What's Changed
- fix: (typescript) generator and async generator types by @gurgunday in 9372d8f
Full Changelog: v3.0.2...v3.0.3
Contributors
Assets 2
v3.0.2
What's Changed
- fix: (typescript) make property readonly by @gurgunday in 33968d1
Full Changelog: v3.0.1...v3.0.2
Contributors
Assets 2
v3.0.1
What's Changed
- feat: (fix) typescript by @gurgunday and @douglasduteil in 0da36e5
Full Changelog: v3.0.0...v3.0.1
Contributors
Assets 2
v3.0.0
This release makes a breaking change to the escaping behavior: we no longer escape the backtick (`) and we now escape the equals sign (=).
Escaping the backtick provided no real protection as it's not a special HTML character. The equals sign, however, is indeed a special HTML character within some parts of a tag.
What's Changed
- revert: escape backtick by @gurgunday in 868abe5
- feat: escape
=by @gurgunday in #24
Full Changelog: v2.3.0...v3.0.0