fix: Update dependencies, ensure build success and add axum-middleware-example

[SiddheshKanawade]

Planned to ensure build with dependencies updated to latest version. Also add axum-middleware-example.

TODO:

• Update dependencies to their latest version. solved Build(deps): update actix-web requirement from 3.0 to 4.1 #71
• Add enable github actions on pull request.
• Both tokio and async-std features of casbin are enabled, disable one to ensure casbin compile successfully
• Make actix-fileadapter-rbac compile successfully after updating the dependencies
• Remove the actix component version conflict and successfully compile actix-middleware-example
• Remove the deprecated calls after updating dependencies and successfully compile ntex-fileadapter-acl
• Add axum-middleware-example
• Make clippy happy

solved #71

[casbin-bot]

@smrpn @hackerchai @PsiACE @GopherJ please review

[hsluoyz]

@hackerchai

[SiddheshKanawade]

@hackerchai do I need to do anything else?

[hsluoyz]

@hackerchai plz review

[hackerchai]

LGTM

[hackerchai]

@SiddheshKanawade Can you also add pull request github actions to run build checks?

[SiddheshKanawade]

@hackerchai I have added the pull_request check and also the cache, not sure the cache will work or not, last time it didn't worked

[hsluoyz]

@SiddheshKanawade plz fix:

[SiddheshKanawade]

The above commits ensures that actix-fileadapter-rbac, actix-pgsql-simple, ntex-fileadapter-acl compiles successfully.

In actix-middleware-example, there are various version conflicts that I am trying to resolve(some examples below). Any suggestions on how should I resolve them? Also, the depedencies shown for actix-casbin-auth aren't updated in crates.io, I think this might be the issue(not sure though). It says that v3 of actix-web is used and not v4.

[email protected]
[email protected]

[email protected]
[email protected]

[email protected]
[email protected]

[SiddheshKanawade]

The possible cure here could be to match the versions of the dependencies to that of the crate.io but then it would restrict us to update the dependencies

[hackerchai]

please fix

[SiddheshKanawade]

please fix

Yeah, I am working on it, its probably due to two different versions of tokio

[SiddheshKanawade]

The crates.io don't have the versions of the dependencies updated, thus had to do following change to allow the use of newer versions of the actix dependencies without conflict
From

actix-casbin= {git = "https://github.com/casbin-rs/actix-casbin", default-features = false, features = [ "runtime-async-std" ]}
actix-casbin-auth = {git = "https://github.com/casbin-rs/actix-casbin-auth", default-features = false, features = [ "runtime-async-std" ]}

To

actix-casbin= {version = "0.4.2", default-features = false, features = [ "runtime-async-std" ]}
actix-casbin-auth = {version = "0.4.4", default-features = false, features = [ "runtime-async-std" ]}

This needs to be updated ones versions are updated in crates.io

[SiddheshKanawade]

@hackerchai I need to get PR #25 merged, so that we have updated tokio version in actix-casbin and avoid the tokio version conflict here. Also, I have completed my work on this PR and can be reviewed once the above mentioned PR gets merged.

[hackerchai]

@SiddheshKanawade plz fix the CI errors

[SiddheshKanawade]

I am not getting this error in my local env, any ideas on how should I cope with it?

[SiddheshKanawade]

@hackerchai All of the tasks have been completed and all checks are passing, kindly review and let me know if I need to do anything else

[hsluoyz]

@SiddheshKanawade plz don't make so big and long-term PRs. You should not make just one PR for the whole summer and put everything in it. Our community's PRs are expected to be small-scale and will be reviewed & merged within 2-3 days, at most one week ideally.

[SiddheshKanawade]

Yeah, actually this repository had a lot to do before I can make build run, so initially the PR became long. Also, this was what I was planning to do initially, but as per instructed by my mentor, I switched to axum-casbin-auth and hence this PR got extended. When I switched back to the task, rather than opening a new PR, I continued to work on this rather than closing it.
Also, your suggestion makes a lot sense and will keep this in mind in future PRs.
Thank You.

[hsluoyz]

OK.

@hackerchai plz review and get this one merged ideally

[SiddheshKanawade]

Since now we have refactored this repository into smaller repositories, this PR has no significance and hence closing it.