jsreport v2 beta released - asking for a feedback
-
Okay, now I"m confused.
I think I got the beta version installed. When I run the studio at localhost:5488, it has a title of "jsreport 2.0.0-beta development'. But when I do a 'npm view jsreport version' I get 1.10.0. I would guess the title of the dev studio means I got the correct version?
Thanks.
-
I think I got the beta version installed. When I run the studio at localhost:5488, it has a title of "jsreport 2.0.0-beta development'. But when I do a 'npm view jsreport version' I get 1.10.0. I would guess the title of the dev studio means I got the correct version?
seems like you have problem with the directories in your machine and this is getting into trouble of how npm installation works. this is a general node.js problem so we can not help here if you don't share more details like what is the full path of your project, how are you running the npm installation? is it just from the command line at the same path of your project directory? if possible please describe all the steps that you are doing, like opening command line at some path, running some command, etc. try to install the v2 beta in clean directory first before trying to update an existing project.
-
Did you get rid of being able to add assets in scripts. In version 1.9.2, I could add a asset to any script by using '{#asset Global-BeforeRender.js @encoding=utf8}'. This allow for some global functions and handling of variables the same way from script to script.
-
hi @hluikartjr no, this should be working fine in v2, i tested it and it works, do you have a case where it does not work? if so, please share some code in playground that does not work in v2
-
@bjrmatos, thanks for the fast response.
The playground link provided above is not working. I found the problem.
I was adding the asset to the top of the scripts outside of any beforeRender function. First line asset looked like this 'var startDate = new Date(req.options.startDate);'
followed by others that refer to 'req.options' where each script would pass the options from script to script.
The error I was getting was 'ReferenceError: req is not defined'.
-
@hluikartjr ahh my bad, anyway great that you were able to solve your issue. for future reference the correct link to playground is this
-
Review of v2:
I like the commit feature. but, it needs a wait wheel or something to indicate that it is working.
The 'Freeze edits' does not allow for running a report from the 'Run'. return 'Error: Editing is frozen through jsreport-freeze extension.
at D:\jsreportV2\node_modules\jsreport-freeze\lib\freeze.js:31:13
at <anonymous>'
Also, 'Release freeze' is not unfreezing and allowing the report to run either.
-
Review of v2:
I like the commit feature. but, it needs a wait wheel or something to indicate that it is working.thanks, agree with you, that operation can take a while with lot of entities and an indicator will be handy indeed.
The 'Freeze edits' does not allow for running a report from the 'Run'. return 'Error: Editing is frozen through jsreport-freeze extension.
at D:\jsreportV2\node_modules\jsreport-freeze\lib\freeze.js:31:13
at <anonymous>'
Also, 'Release freeze' is not unfreezing and allowing the report to run either.i can confirm this bug with freeze extension, thanks for taking the time to test it, we will fix it
-
This is more of a feature then a bug. could the 'freeze edits' be per item not globally. The reason for this is we use some global scripts that need modifying, while most of the script do not. It would be good to lock editing on the ones that should never be modified and allow editing on the ones that will be modified.
-
@hluikartjr Thanks for the idea. We were discussing this feature and it seems to us that you should rather use authorization in this scenario. You could create an extra user with read only permissions to all entities and write permissions to those you consider safe to change. The freeze should always block everything in our current opinion. However we are open to change of course.
