<commit_before>TODO:

1. inherit state "secured" property (decorator like 'data' on config)
2. add "fetchingRoles" to config, remove assumption about getting roles from login
    and return the actual login promise



security guards

path guard - asks questions...
    is this path secured?
    show me an access card (temp id)...
    is this person allowed in this path?



render guard -
 should you be allowed to see this portion of the template?

http guard
should you be allowed to see this data?

login phase -

login http request -> response logic -> roles, permissions, (token / session id)

<commit_msg>add a reminder<commit_after>TODO:

1. inherit state "secured" property (decorator like 'data' on config)
2. add "fetchingRoles" to config, remove assumption about getting roles from login
    and return the actual login promise,
3. add timeout logic to angular-cache and not just FOREVER



security guards

path guard - asks questions...
    is this path secured?
    show me an access card (temp id)...
    is this person allowed in this path?



render guard -
 should you be allowed to see this portion of the template?

http guard
should you be allowed to see this data?

login phase -

login http request -> response logic -> roles, permissions, (token / session id)


{'fraction_non_alphanumeric': 0.06293706293706294, 'fraction_numerical': 0.003885003885003885, 'mean_word_length': 3.4567474048442905, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '171847', 'n_tokens_mistral': 346, 'n_tokens_neox': 331, 'n_words': 188}