Upgrade to v3
Help developers to move from v2 to v3. Please read carefully and integrate the following breaking changes to ensure a smooth update.
Last updated
Help developers to move from v2 to v3. Please read carefully and integrate the following breaking changes to ensure a smooth update.
Last updated
Please be sure of your agent type and version and pick the right documentation accordingly.
This is the documentation of the forest-express-sequelize
and forest-express-mongoose
Node.js agents that will soon reach end-of-support.
forest-express-sequelize
v9 and forest-express-mongoose
v9 are replaced by v1.
Please check your agent type and version and read on or switch to the right documentation.
Set CORS credentials: true
if you're using custom CORS configuration.
Smart actions defined as follows global: true
will no longer be considered as global.
Please now use type: 'global'
.SQLMongodb
Before
After
On server start - only in development environments - the agent will generate a .forestadmin-schema.json
file reflecting your Forest Admin models.
If you change your models, Forest Admin will automatically load a new schema to keep the layout up to date. However, note that changes in your database will not be reflected in your models nor in your UI, unless you use lumber update
(for Lumber) or update your models manually otherwise.
Do not edit this file. It will be automatically generated on server start only in development environments.
This file must be deployed for any remote environment (staging, production, etc.), as it will be used to generate your Forest Admin UI.
Version this file. It will give you more visibility on the changes detected by Forest Admin.
In the following example, we have added two fields on the invoices
table:
emailSent
quadernoId
This release note covers only the major changes. To learn more, please refer to the changelogs in our different repositories:
Versioning the.forestadmin-schema.json
file allows you to easily visualize the changes..forestadmin-schema.json versioning example