Skip to content
  • Looks neat! Is the main idea here the DSL and the simplified reasoning it enables?

    The roles storage I think is functionally equivalent to teams, with their teamTypes and objectId.

    Does the DSL deal with property filtering as well? The definition/parsing of these expressions could be a very non-trivial effort.

    In general I think it would be better to drive the implementation a DSL from fully hashed out Authsome modes (let’s take Editoria and the xPubs as primary sources), as opposed to the other way around, developing a DSL and then trying to make it fit the requirements.

  • Is the main idea here the DSL and the simplified reasoning it enables?

    Yes.

    Does the DSL deal with property filtering as well?

    No. What's an example use case for that?

    The definition/parsing of these expressions could be a very non-trivial effort.

    Yes! I've been wanting to write a parser since I started writing a toy compile-to-JS language last year. A more pragmatic approach might be to use plain JS:

    // Role config
    
    export const Unauthenticated = {
      'read book': ({book}) => book.status === 'published', 
      signup: true,
    }
    
    export const Author = {
      ...Unauthenticated,
      'read book': true,
      'edit book': ({book}) => book.status !== 'published',
      'submit for approval': true,
    }
    

    Agree that we need a more complete example mode before we can design something that's likely to cover all bases.

  • I am not a pretty big learner and your code seems to be very easy to me as I was learning too for my study to complete anytime soon with help of personal statement writing service online where I am getting a huge discount that is a so mcuh relax to me

  • Every business has unique needs and the one-size-fits-all software solutions often fall short. The custom software development service offered on Custom Software Development Services seems like a beacon for those in search of tailor-made solutions. The page articulates a client-centric approach, focusing on understanding the unique requirements and delivering a solution that fits like a glove. The detailed explanation of the process, coupled with the mention of agile methodologies, reflects a structured yet flexible approach to software development.

0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment