Two fixes. A data-render turning on no longer clears a pool's bindings: when a data-render condition started false and later became true, rows in a data-pool elsewhere in the same component lost the values set by their own data-bind-attr, so a bound image went blank while the pool entity still held the right string. Re-inserting the section rescans the component for bindings, and that scan claimed the pool's rows, then evaluated each row's expression in component scope where the entity's fields do not exist. undefined and null query values are left out of the URL: navigate(path, { query: { search: term || undefined } }) is the ordinary way to leave a key off, and it wrote the literal string undefined, which the next page load read back as a real filter value. An empty string is still kept, since ?q= says something different from no q at all.
Fixed
- A data-render turning on no longer clears the bindings of a data-pool in the same component (every tier)
- undefined and null query values are omitted from the URL rather than serialised as strings (spa and full)
Full details in the changelog (https://www.wildflowerjs.com/changelog.html#v1-5-2).