Samuel Degueldre 02a187d80b [FIX] compiler: fix falsy values for properties not keeping input empty ...

Recently, we made it so that when a component is rendered, it always
updates the property values for computed properties. This was done by
wrapping the value in a String or Boolean object. One issue with this is
that wrapping a falsy value in a String doesn't yield an empty string,
but a string containing the value as text (eg new String(undefined) ->
"undefined"), which causes the value to not remain empty as per the
spec. This commit fixes that by adding a fallback to the empty string
for falsy values before converting to a String object.

closes: #1236

2022-08-05 09:50:38 +02:00

..

__snapshots__

[FIX] properly get component reference instead of context

2022-06-22 16:15:54 +02:00

app

[REF] move component function to app, improve some code

2022-06-13 09:51:31 +02:00

blockdom

[REF] runtime: rename handler.ts -> event_handling.ts

2022-05-31 14:00:01 +02:00

compiler

[FIX] compiler: fix falsy values for properties not keeping input empty

2022-08-05 09:50:38 +02:00

components

[FIX] components: fix cause left unset when thrown object is not Error

2022-07-22 09:21:19 +02:00

misc

[IMP] *: use a custom error class for all errors thrown by owl

2022-07-18 15:40:14 +02:00

mocks

[REF] initial prototype of owl 2

2022-02-11 10:18:01 +01:00

tooling

[FIX] doc: fix broken link, and fix doc link checker test

2022-02-11 10:46:44 +01:00

helpers.ts

[IMP] *: use a custom error class for all errors thrown by owl

2022-07-18 15:40:14 +02:00

reactivity.test.ts

[REF] reorganize file structure

2022-05-31 14:00:01 +02:00

utils.test.ts

[REF] reorganize file structure

2022-05-31 14:00:01 +02:00

validation.test.ts

[IMP] validation: add support for value types

2022-06-15 08:56:44 +02:00