Trying it I found this problem:
Previously I installed:
npm install -g npm@latest
npm install -g typescript
npm install -g @angular/cli@latest
In Radzen beta Output window when try to run:
ng-cli: An unhandled exception occurred: Cannot find module 'typescript'
Initially tested by creating New Radzen sample app Find a Car with default theme.
Not sure if these issues are related to the new version or if the app needs an update but will post anyway.
Another strange issue is the Radzen Beta IDE was working but it has now started loading but the new application and import icons are missing and most of the menu items no longer work. E.G. clicking the File Import no longer does anything. Only a single instance of Radzen Beta is running and log.txt does not report any errors. After restarting windows the Radzen Beta is still not working.
FYI:After reinstalling the Radzen beta it is now working again.
There is indeed such a version of the @radzen/angular package. You need to install
The missing typescript package is an issue that we will fix and update the build.
It looks as there is a theming issue with the Scheduler. We will investigate.
Just updated the download links to a newer Beta release - Radzen 2.60.0-beta.1. Fixes include:
- Radzen cannot find the
typescriptpackage when building.
- Radzen asks you to install @firstname.lastname@example.org which does not exist. Now it should correctly tell what version to install.
- The scheduler button colors are off in some themes.
Using Beta-1. Windows
I have to run the Radzen application as Administrator to compile and run the application : otherwise complains about not being able to create a ".cache " folder onder node_modules.
@mcanavar unfortunately this seems to be an Angular CLI issue that we can't do much about. Does it happen if you run
npm install in the
client to have a copy of node_modules instead of using the linked one?
when using "npm install" the issue with having Radzen run in admin mode resolves, so it seems to be only the issue when the linked npm version is used.
@mcanavar is Radzen installed by this user?
A possible solution is to give write access to
C:\Program Files\Radzen to your user. We will investigate if there are other ways to solve this problem.
UPDATE: We seem to have found a way to move the cache directory to the application itself instead of node_modules. Will ship with the next update of the Radzen Beta.
Does Radzen automaticallay update packages in package.json and if so when? I just imported a project and got lots of errors similar to.
Manually updated package.json with "@radzen/angular": "next", and now works without error although some formatting issues within app so likely need to update some other references.
Update:Was using premium dark theme and modals appearing to left and translucent. Changed theme in settings then restored, rerun and now modals appear correctly.
@mumfie yes, Radzen should have updated the version automatically but I think there is a case where it won't. Will handle that. About the theming issue - indeed some PrimeNG components have changed rendering hence we had to update the themes. Mentioned above in the "What changed" section.
when opening a page as a dialog it is displayed semi-transparent and in the left top corner. No custom code was added to the action - just the logic of the automatically generated CRUD page. Deleting the on-click logic and adding it again did not result in any change. Despite its weird appearance, the opened dialog is still functional - one can press buttons and open dropdown-fields...
Forgot to add - tested in Chrome v 84.0.4147.135 and MS Edge v 84.0.522.63
Theme used is the Default one, with primary color changed manually in \client\src\assets\css
My last response discusses this very issue. You need to reset your custom theme.
Just doing some preliminary testing using 2.60.0-beta.1 and noticed an error coming up on a couple of my dialogs when they are opened. They are simple add and edit dialogs with nothing complicated on them but, this error is showing in the console:
Having deleted objects off the page 1 at a time, I've got down to the error coming from a Checkbox component which has it's Value property bound to a boolean page property
To my regret this seems buried deep in the Angular code and I can't trace it to Radzen. Can you send us your application to email@example.com so we can investigate further? Also specify what page this happens in. Thanks!
I have just updated the Radzen Beta and the download links in the first post. There are two things fixed in the new version.
- The issue reported by @markb - having a CheckBox in a Template form throws a runtime JS error.
- The user cannot select tables in the data source infer dialog - the tree component does not respond to user action.
Just tried this new beta version and still unable to uncheck anything (tables,columns, etc) in the Entities fieldset.
If check Generate pages for CRUD operations can amend checkboxes in CRUD Pages fieldset.
Indeed we have uploaded a build which does not include the fix. Will do so next week.
@mumfie, we updated the beta build links with a fix for this issue.