trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

web: prettier had opinions about the README

This commit is contained in:
Ken Sternberg 2023-12-04 09:52:04 -08:00
parent d4b80c17e8
commit d2a9b2a343
1 changed files with 47 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
web/README.md
View File

@ -7,7 +7,7 @@ for awhile, but at least let's get started.
In Peter Naur's 1985 essay [Programming as Theory
Building](https://pages.cs.wisc.edu/~remzi/Naur.pdf), programming is described as creating a mental
model of how a program *should* run, then writing the code to test if the program *can* run that
model of how a program _should_ run, then writing the code to test if the program _can_ run that
way.
The mental model for the authentik UI is straightforward. There are five "applications" within the
@ -46,7 +46,7 @@ experience:
**Mental Model**
- Upon initialization, *every* authentik UI application fetches `Config` and `CurrentTenant`. `User`
- Upon initialization, _every_ authentik UI application fetches `Config` and `CurrentTenant`. `User`
and `Admin` will also attempt to load the `SessionUser`; if there is none, the user is kicked out
to the `Flow` for logging into authentik itself.
- `Config`, `CurrentTenant`, and `SessionUser`, are provided by the `@goauthentik/api` application,