Node-Casbin@6 planning

[nodece]

Node-Casbin@6 full-support any JavaScript platform like React Native, Electron, and so on.

Branch: https://github.com/casbin/node-casbin/tree/beta

I make some planning for this version:

• Only support pass the Model instance, Adapter instance and enableLog to newEnforcer(), avoid confusing that use path or text
• Cleanup the code with "path", "file"
• Collect the breaking changes, which is used to make a migrate doc

[casbin-bot]

@Gabriel-403 @Zxilly @kingiw @nodece

[Shivansh-yadav13]

Hey @nodece, I would like to contribute to this, I want to confirm that we are planning to sort of rebuild the newEnforcer() and going to pass in 3 params right?

[nodece]

Yes, but some parameters are optional, so like:

newEnforcer(model)
newEnforcer(model, adapter)
newEnforcer(model, adapter, true)

// Not sure if is correct behavior.
newEnforcer(model, true)

We can open this issue for a while to discuss.

[Shivansh-yadav13]

ohk then I guess for a request like this

newEnforcer(model, true)

we can maybe keep ...params: any[] in the newEnforcer() and then pass them in a fixed manner in newEnforcerWithClass(model, adapter, true)

[nodece]

Both newEnforcer() and newEnforcerWithClass params need to changes.

[Shivansh-yadav13]

@nodece, there are no breaking changes on params change in the tests at least.

[nodece]

We remove some API with fs or path, this is breaking changes.

[hsluoyz]

We don't have the ability to control the damage caused by the breaking changes based on our developer resources. So we don't accept any kind of breaking changes.

[wittech]

how to config muti policies?

[Shivansh-yadav13]

@wittech if you have a question, you can ask in the Gitter channel https://gitter.im/casbin/Lobby

[nodece]

Migrating to https://github.com/casbin/casbin-core for this thing.