Herby Vojčík
unread,Jul 10, 2021, 10:23:24 AM7/10/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message as abuse
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Amber ML
Hello all!
================
ANNOUNCEMENT
================
New patch version release is out, the 0.30.1
TL;DR:
npm -g install @ambers/cli
and your new projects will be created with new version.
For cases where npm think it knows better (and new project is still
based on older version, find out in package.json), try:
npm -g install @ambers/cli -f
and if even that does not help, this should:
npm -g uninstall @ambers/cli -f
npm cache clean -f
npm -g install @ambers/cli -f
===================
THE CHANGES
===================
From CHANGELOG:
* A few convenience APIs.
* One bug fix.
The convenience APIs relate to the case when #{...} syntax is not
helpful with JS libs which are picky and actually demand literal JS object.
In this case, you can create empty JS Object via
JSObjectProxy newObject
then update it with at:put: and finally read raw value with jsObject;
or you can use #{...} syntax if it only contains literals and pass
#{ #foo -> 'bar'. #baz -> { 3. 1. 4 } } jsonLiteralize
to the picky library. The latter does JSON roundtrip (make JSON string
out of the receiver and parses it back). Should help in most such cases.
================
UPGRADE PROJ
================
To upgrade your not too old project, this should suffice:
npm install @ambers/lang@^0.30.1
grunt
The mechanical, though needing a bit of tools expertise, although
working, way to do the upgrade of older project is to create new project
with `amber init` with the same name as the old project, copy the files
over to old project, and go over the diffs (shown by git / IDE / both)
manually.
Herby