From 87f335c18722e4243faa2aff6cd021458213ba19 Mon Sep 17 00:00:00 2001 From: Ana Bujan Date: Tue, 8 Mar 2022 16:13:28 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 78ea590..1e31516 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # Actix Permissions [![Continuous Integration](https://github.com/eisberg-labs/actix-permissions/actions/workflows/ci.yml/badge.svg)](https://github.com/eisberg-labs/actix-permissions/actions/workflows/ci.yml) [![cargo-badge][]][cargo] [![license-badge][]][license] Permission and input validation extension for Actix Web. Alternative to actix guard, with access to app data injections, HttpRequest and Payload. -Permissions are flexible, take a look at [Examples directory](./examples) for some use cases. +Permissions are flexible, take a look at [Examples directory](./examples) for some of the use cases. You could write a permission check like a function or like a struct. This code: @@ -91,7 +91,7 @@ async fn main() -> std::io::Result<()> { ## Use Cases Take a look at [Examples directory](./examples). You could use actix-permissions for role based authorization check, like in *role-based-authorization* example. -*hello-world* example is just proof of concept, showing how you can compose a list of permissions, +*hello-world* example is just a proof of concept, showing how you can compose a list of permissions, access service request, payload and injected services. ## Contributing