Let us specify different datatypes for each entity's action.

[grunklejp]

  export const permix = createPermix<{
    post: {
      action: "read" | "create";
      dataTypes: {
        read: Post,
        create: Omit<Post, "id">, //  the database auto creates the id 
      };
    };
  }>();

We create a new property called dataTypes (minor version upgrade).

Then in the check() these types will be strongly typed for these actions.

Currently I have to rely on a partial object for all of the actions and this is annoying because I need to constantly reference my permissions to make sure i have the required properties on the object.

---

What is neat about this is if you need a compound datatype you can just pass a higher level object. {post, user}

[letstri]

Thanks for your issue!

Good suggestion, I'll try to implement it, but I don't know when yet.

[grunklejp]

Just to make it explicit why i think this is so needed. In permix's current implementation doing ABAC is very limited. You are essentially required to provide attributes (outside of your main resource, aka dataType) at setup time. I like to call setup once with all my apps permissions in a middleware right when a request is received, stick the permix object in AsyncLocalStorage and pull it out whenever i need to check permissions.

If you allowed each individual action to specify its dependencies (required to be passed through the check()) you can fetch as needed. Most importantly the check usage documents exactly which additional attributes it needs, no matter how complex that action's required attributes are.

  export const permix = createPermix<{
    post: {
      action: "read" | "create";
      dataTypes: {
        read: Post,
        create: {
          post: Omit<Post, "id">,
          subreddit: {
            userKarma: number,
            userJoinedAt: Date,
          }
        },
      };
    };
  }>();

check(
  'post', 
  'create', 
  {
    post,
    subreddit: {
      userKarma,
      userJoinedAt,
    }
)

[letstri]

Thank you, I'll think about how to do it

In the current implementation, it is impossible to do this while maintaining backward compatibility, because we need to dynamically build a type for an action prop that is not yet known.

[grunklejp]

I played around with this and ended up publishing a very barebones version that has most of what i want https://github.com/grunklejp/access-mini

But yeah turns out it's hard to make a nice typesafe api for this

[letstri]

I started sketching out some options, it turned out not bad, but there are difficulties that I don't know how to fix yet.