Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hibiki v0.3.0 Release #4

Merged
merged 32 commits into from
Feb 14, 2022
Merged

Hibiki v0.3.0 Release #4

merged 32 commits into from
Feb 14, 2022

Conversation

sawka
Copy link
Contributor

@sawka sawka commented Feb 14, 2022

No description provided.

…ute, define-vars can receive inner html text, custom nodes fire init event, do not throw an error when setting read-only values (silently ignore), h-text shows '[noattr]' when formatting noattr value.
…LambdaValue. Bug fixes for and/or operators when dealing with noattr values
…es not resolve intuitively when ChildrenVar is null.
…xpanded recursively in a consistent way, still bound to their proper scope, and merged correctly even with multiple levels of h-children attribute injection. removed childrenvar.list and replaced with childrenvar.node and childrenvar.nodes. conistent handling of if-break and define-vars even when passed to children
…ender. new createspecials datactx function which creates a new context map without using setPathInternal (so it is mobx safe). fixed issue with nested lvalues (bulma modalbutton)
…ki.ts module. more straightforward. moved configuration for suppressing these messages to a global config object.
…-parser. add fn:ceil and fn:floor. remove h-withcontext (define-vars is more powerful)
…ne-handler). remove old isEditMode code from dbctx
…sensitivity, string/numeric, case insensitivity
…e type conversions to satisfy typescript and make hibiki functions less likely to throw errors when passed invalid types
… references stored in context variables. needed for advanced use cases like nested components and inline editing of sorted or sliced data (that retains its link to the original data)
…r == null. add new isnoattr() expression to distinguish noattr from null (because of '==' change).
…act warning about whitespace nodes. browser just silently ignores them (as react should)
@sawka sawka merged commit e73e43d into main Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant