-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve UX on config page #27
Conversation
scope listArgumentsByType to correct form Select arguments by class instead of type
start making enabled folders checklist-able Implement save/load folder lists change enabledfolders to checklist refactor: rename saveFolderList -> serializeEnabledFolders, fillFolderList -> populateEnabledFolders refactor listArgumentsByType start implementing load provider role mapping implement role mapping Move remove button markup, change hierachy remove logging statements resolve folder population promise before trying to check folders
@9p4 ready for review |
I request a release be made to the manifest upon this PR's merge |
Sure, I'll put out a new release (maybe not 4.0 though) |
Looks good, but I would prefer the multi-line textareas to be below the slug instead of inline. Furthermore, I think there needs to be a tiny bit more info for "Roles" and "Admin Roles" and whether or not the roles are separated by newlines. |
I'm not sure what you mean by that, this is what they look like to me Unless you mean the folder role mapping inputs Also, by "slug" do you mean the input labels?
good point |
Add stylesheet update markup + styling of specialized forms improve markup, assign checkboxes as emby-checkbox es imrpove markup, remove old comments run stylesheet through prettier Update help strings
![2022-05-14-20-36-33](https://user-images.githubusercontent.com/17993169/168452556-e1772a12-aacb-4c03-87e4-61d103984202.png)
Ew! Looks terrible! I'll try it on Firefox, I copied the textarea styling over from Jellyfin's, since for some reason they don't expose the textarea stylesheet to plugin pages, and maybe there was something missing |
scope listArgumentsByType to correct form Select arguments by class instead of type
start making enabled folders checklist-able Implement save/load folder lists change enabledfolders to checklist refactor: rename saveFolderList -> serializeEnabledFolders, fillFolderList -> populateEnabledFolders refactor listArgumentsByType start implementing load provider role mapping implement role mapping Move remove button markup, change hierachy remove logging statements resolve folder population promise before trying to check folders
Add stylesheet update markup + styling of specialized forms improve markup, assign checkboxes as emby-checkbox es imrpove markup, remove old comments run stylesheet through prettier Update help strings
It looks fine on all my browsers, it kind of looks like the entire stylesheet isn't being loaded Check devtools console- Is this code running okay? Is the stylesheet 404'ing? I've introduced the stylesheet as another embedded asset, is something going wrong there? Looks liek your folder lists & role mappings also aren't recieving custom styling, so my best guess is the entire stylesheet isn't making it into your build. |
Seems like the stylesheet isn't loading when Jellyfin is served under a subdirectory. |
Should be Seems like a bug in JF. The proper URL (/jellyfin/web/configurationpage?name=SSO-Auth.css) loads the stylesheet so the issue is the frontend that isn't adding in the right URL. |
Scratch that, it's a bug in the JS
|
Alright it seems to be all fixed now. |
Just checked and it doesn't seem like the per-provider allowed folders isn't working either (POSTing an empty array, doesn't populate) |
Alright, those issues should all be fixed now. Let me know your thoughts before I merge. |
I'll have a look, but if it's all good from your end, I'm happy. |
LGTM, thanks for fixing those issues up. |
Resolves #2
Done:
Input validationOptional json fields should send empty placeholderAllow configuration of OIDC scopes to request to support role-claim #23 (comment)(JSON is not acceptable long term)
Add UI Page for OIDC Configuration #18 (comment)
Options:
Implement some kind of list-append dialog, similar to builtin library / folder management (More complex, better (?) UX)