angular-starter-project

• Added grid export to excel method - demo in UsersComponent
• Added ability to allow the user to store the order of columns on the grid, by setting the columnOrderStateKey grid setting
• Added example of enhancing remult's FieldOptions to allow defining in the entity how one would select a value in the ui.
  • Added clickWithUI - to FieldOptions. See Using click with ui article
• Added example of custom data control to be used in data area and data control
  • Added customInput - to FieldOptions See Using custom input article
• Renamed DialogService to UIToolsService
• Renamed InputAreaComponent to DataAreaDialogComponent

In this version we've made several changes:

1. Introduced Remult 16, with easier ways of writing code.
2. Removed the dependency on @remult/angular and included its code in this project.
3. Replaced the security implementation from using jwt to using a more secure cookie session

Remult 16

In this version, we've upgraded to remult 16 which provides a general remult that can be used, instead of sending remult as a parameter all over the code.

Here are some examples:

1. Angular Component:
   

   • You no longer need to receive Remult in the constructor
   • You no longer need to use this before remult

2. Backend Method:
   

   • You no longer need to recieve an optional remult object in a backend method.
   • You no longer need the '!' after remult when writing remult.repo

3. Entity options
   

   • When you need remult in an options object, you no longer need to use the more complex arrow function '(options,remult)=>`

Removed the dependency on @remult/angular and included it's code in this project.

The dependency on @remult/angular was removed and the entire source of DataArea, DataGrid, and DataControl was moved into this project, to make it easier to customize flexibly

Replaced the security implementation from using jwt to using a more secure cookie session

We no longer depend on JWT and store nothing in the Local/session storage.

For more info read Local Storage Versus Cookies: Which to Use to Securely Store Session Tokens

Note that the session secret is now named 'SESSION_SECRET' - remember that when you deploy (to Heroku or anything else)

Code diff:

Code diff