N00b question. I have created an unholy alliance between fulcro-rad-demo and the React Native demo code. I have jumped through several hurdles already but my EQL and Pathom skills are in their infancy. I do not understand why the below query is causing the RAD demo parser to throw an exception:

[{:com.wsscode.pathom.connect/indexes [:com.wsscode.pathom.connect/idents :com.wsscode.pathom.connect/index-io :com.wsscode.pathom.connect/autocomplete-ignore]}]

@hadilsabbagh18 When you say “the query is coming from Fulcro Inspect Electron” do you mean that you entered that query in the EQL tab and got the expected result?

No @alex-eberts. This is a query that Fulcro Inspect Electron sends to load the Pathom indexes for the EQL window.

I’m looking for a little guidance on authorization of various parts of my app (non-RAD). I have an authentication flow and UISM similar to what RAD provides that allows for auth using AWS Cognito. I have a set of user permissions in my state. What I’m unclear on is where is the best layer in the app to enforce authorization. I have simple router hierarchy. Some things I’d like to be able achieve: 1. Have a authenticated and non-authenticated authorized routes 2. Have authorization on particular components, say comparing the user permissions to the set of permissions on the components 3. Perhaps even have authorization on the query. RAD provides a few hints of authorization against attributes but purposely avoids an implementation as it’s a minefield. At this state all front end. I’ll sort parser security at a later stage. What I’m looking for is a little guidance on which hooks in the system to use. For this kind of functionality should I be using allow-route-change? on the routes? Should I build an authorizing router that can wrap other components? Should I be using render-middleware? Should I just have a defsc or function that can do this for me? I want to keep the simplicity and performance that fulcro provides. I’m a little lost and would love a push in a particular direction, perhaps even a strong shove! Where to begin or how have others done it?

I’m thinking that I should just take the RAD approach: Have a Session component that queries on the authentication state as well as the user permissions, then just use those directly in components that require them.