trustchain-oc1-orchestral/authentik
Archived
10
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
This repository has been archived on 2024-05-31. You can view files and clone it, but cannot push or open issues or pull requests.
authentik/web/xliff
History
Ken Sternberg bb52765f51
web: refactor sidebar capabilities for categorical subsections (#7482) 
* web: break circular dependency between AKElement & Interface.

This commit changes the way the root node of the web application shell is
discovered by child components, such that the base class shared by both
no longer results in a circular dependency between the two models.

I've run this in isolation and have seen no failures of discovery; the identity
token exists as soon as the Interface is constructed and is found by every item
on the page.

* web: fix broken typescript references

This built... and then it didn't?  Anyway, the current fix is to
provide type information the AkInterface for the data that consumers
require.

* web: rollback dependabot's upgrade of context

The most frustrating part of this is that I RAN THIS, dammit, with the updated
context and the current Wizard, and it finished the End-to-End tests without
complaint.

* Due for amendment

* Revert "Due for amendment"

This reverts commit 829ad5d3f2.

* web: refactor sidebar capabilities for categorical subsections

The project "Change Admin UI lists to have sublists per type" requires some initial changes to the
UI to facilitate this request. The AdminSidebar is the principle target of this project, and it is
embedded in the AdminInterface. To facilitate editing the AdminSidebar as an independent entity,
AdminInterface has been moved into its own folder and the AdminSidebar extracted as a standalone Web
Component. This removes, oh, about half the code from AdminInterface. A little cleanup with
`classMap` was also committed.

The rollup config was adjusted to find the new AdminInterface location.

The Sidebar uses the global `config: Config` object to check for Enterprise capabilities. Rather
than plumb all the way down through the Interface => AdminInterface -> AdminSidebar, I chose to make
provide an alternative way of reaching the `config` object, as a *context*. Other configuration
objects (Me, UiConfig, Tenant) interfaces will be contextualized as demand warrants.

Demand will warrant.  Just not yet. <sup>1</sup>

The Sidebar has been refactored only slightly; the renderers are entirely the same as they were
prior to extraction. What has been changed is the source of information: when we retrieve the
current version we story *only* the information, and use type information to ensure that the version
we store is the version we care about. The same is true of `impersonation`; we care only about the
name of the person being impersonated being present, so we don't store anything else.

Fetches have been moved from `firstUpdated` to the constructor.  No reason to have the sidebar
render twice if the network returns before the render is scheduled.

Because the path used to identify the user being impersonated has changed, the `str()` references in
the XLIFF files had to be adjusted. **This change is to a variable only and does not require
translation.**

---
<sup>1</sup> The code is littered with checks to `me()?`, `uiConfig?`, `config?`, etc. In the
*context* of being logged in as an administrator those should never be in doubt. I intend to make
our interfaces not have any doubt.

* Function to help generate sizing solutions across Javascript and CSS.

* web: refactor sidebar capabilities for categorical subsections

Move open/close logic into the ak-admin-sidebar itself.

This commit removes the responsibility for opening/closing the sidebar from the interface parent
code and places it inside the sidebar entirely.  Since the Django invocation passes none of the
properties ak-interface-admin is capable of receiving, this seems like a safe operation.

The sidebar now assumes the responsibility for hooking up the window event listeners for open/close
and resize.

On connection to the DOM, and on resize, the sidebar checks to see if the viewport width meets the
criteria for a behavioral change (slide-overlay vs slide-push), and on slide-push automatically
opens the sidebar on the assumption that there's plenty of room. In order to support more dynamic
styling going forward, I've substituted the 1280px with 80rem, which is the same, but allows for
some better styling if someone with older eyes needs to "zoom in" on the whole thing with a larger
font size.

The hide/show code involves "reaching up" to touch the host's classList.  There's a comment
indicating that this is a slightly fragile thing to do, but in a well-known way.
2023-11-20 10:24:59 -08:00
..
de.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
en.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
es.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
fr.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
nl.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
pl.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
pseudo-LOCALE.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
tr.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
zh-Hans.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
zh-Hant.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
zh_CN.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00
zh_TW.xlf web: refactor sidebar capabilities for categorical subsections (#7482) 2023-11-20 10:24:59 -08:00