Query: Upgrade from v7 to v8

Help me!
1

Note: Nothing impacted till now i am just want to clarify things before migrating from v7 to v8.

Feature(s) impacted

Scopes.

Observed behavior

breaking change mentioned in doc https://docs.forestadmin.com/documentation/extra-help/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8#breaking-changes
I am referering to above mentioned doc while stating my query
screenshot for reference:

image
image1920×1080 294 KB

code which is closely relevant to the area of my concern.

Main Query: i want to know that if i will upgrade my agent version for forest admin server from v7 to v8, then there is a possiblePreformatted text breaking change mentioned in doc https://docs.forestadmin.com/documentation/extra-help/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8#breaking-changes , whether scopes related breaking changes are only for permissionMiddlewareCreator.smartAction() or will they impact our code which is simple knex migration create related code :

code example:

router.post('/knex_migrations_lock', permissionMiddlewareCreator.create(), (request, response, next) => {
 routes#create-a-record
  next();
});

supporting screenshot:

image
image1750×569 76 KB

Context

  • Project name: Blush Now
  • Team name: blush now
  • Environment name: My concern is related to all envs (as migration will be project level)
  • Agent (forest package) name & version: forest-express-sequelize(want to go from v7 to v8)
  • Database type: postgres (using sequelize orm)
2

Hello @Mukesh_Bisht,

Thanks for reaching out :raised_hands:

I think I understood your question.
To make it simple on the Scope breaking change: you need to check if you have any occurrence of RecordsGetter , RecordCounter , RecordsExporter , RecordsRemover , RecordCreator , RecordGetter , RecordUpdater , RecordRemover and RecordsCounter.
If you do, then you need to change a bit their signature.
If you don’t, you can ignore this change to make!

If you don’t use any smart action, you probably don’t use those methods indeed. But please double check, it won’t cost you a lot to verify.

Let me know if that helps.
Cheers!

1 Like
3

hi @anon34731316 thanks for your quick support.

1 Like