Changelog
[3.3.0] - 2023-02-07
Added
-
#154: it is now possible to reuse the context from one run to another, e.g. keeping the knowledge of what was said, the synonyms triggered etc. See Save context documentation.
[3.2.6] - 2022-10-30
[3.2.0] - 2022-01-22
Added
-
#109: There can now be 2 levels of assembly in
eachz
anditemz
. See in 2 levels assembly in eachz/itemz doc.
[3.1.2] - 2022-01-04
Fixed
-
\#
present in documentation are now corrected in#
(thanks to recipe https://github.com/asciidoctor/asciidoctor/issues/3415)
[3.0.0] - 2021-05-06
It is a major version because there are breaking changes.
Added
-
you may use RosaeNLG without using templates, accessing directly the low level JavaScript API; support is experimental. See Usage without Pug templates
-
there are now some "universal tenses" defined, which work for multiple languages; see Universal tenses table
Changed
There are 3 breaking changes that affect existing templates.
ref
and refexpr
must be reference to mixins
ref
and refexpr
must now be reference to mixins (and no more strings), and they must be referenced after being declared.
Before |
---|
- var PRODUCT = {}; - PRODUCT.ref = 'PRODUCT_ref'; mixin PRODUCT_ref(obj, params) |
the ring …. |
After |
- var PRODUCT = {}; mixin PRODUCT_ref(obj, params) |
the ring - PRODUCT.ref = PRODUCT_ref; …. |
Your templates will probably fail at runtime if you don’t change them. To migrate:
-
search for
.ref
and.refexpr
in your templates -
put references instead of strings
-
move them after the referenced mixin declaration
when referencing a mixin, assembly separators properties must not use a string
Assembly separators (last_separator
, begin_with_general
, etc.) can either be a string or reference a mixin.
When referencing a mixin, you must now put the mixin as a reference (no more as a string), and the mixin must have been defined before.
If you don’t migrate, your templates will not fail, but the text will be wrong: you will have the mixin name in the output.
To migrate, search for all assemblies (eachz
and itemz
) and change their properties if they reference mixins.
mixins and objects cannot have the same name
Mixins are now functions, which have a name; you cannot have mixins and objects having the same name, e.g.
mixin phone | bla bla - var phone = {};
is now invalid.
Your templates will probably fail at runtime if you don’t change them. Rename conflicting mixins or objects.