Hi,The nice thing about hobo is that it is easy to test complex permission situations through your model tests. take a look at https://groups.google.com/d/msg/hobousers/XMpolsF5Ty8/63wLKVw-5mwJ for how I do it.
Regards, Henry On 17/07/15 12:05 PM, Nathan Peters wrote:
I'm starting a new Hobo project that is going to have a very complicated (to my experience) permission structure. It is a process control app. Visibility on some things will be controlled both by date and by active user. Users will not even be able to see certain things until a target date, at which point they will have edit rights which should be removed after a second target date. In short, it is heady stuff.Any tips as I delve into this type of thing? Are there some examples out there (on GitHub or other) that would be a good reference as I think about more complicated process permissions in Hobo?Thanks, Nathan --You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
-- Henry Baragar Instantiated Software Inc. http://www.instantiated.ca -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
<<attachment: Henry_Baragar.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
