8 Commits

Author	SHA1	Message	Date
Harvey Tindall	db1c62cc46	jellyseerr: cleanup requests method, read proper errors ... single req() function is wrapped by methods for each http method, and error messages are parsed and returned if given by the server. also added note about Jellyseerr's enforcement of unique email addresses in settings.	2024-07-31 15:31:11 +01:00
Harvey Tindall	385953b0cb	jellyseerr: fix email setting, cover all contact adjustment areas ... hopefully all places where contact methods can be adjusted should sync with jellyseerr.	2024-07-30 20:55:45 +01:00
Harvey Tindall	35f8337a36	jellyseer: revert auto-nulling of NotifTypes ... All-zeros in NotifTypes means the user shouldn't receive any communication, which is a state we'd like to store in/apply from a profile.	2024-07-30 16:53:40 +01:00
Harvey Tindall	769a7c45da	jellyseer: auto-null NotifTypes field ... changed to a pointer so it can be nil-ed, and an Empty() receiver method is used to check if it needs it in ApplyNotificationsTemplateToUser.	2024-07-30 16:49:35 +01:00
Harvey Tindall	a97bccc88f	jellyseerr: use in profiles, apply on user creation and modification ... added in the same way as ombi profiles. Most code is copy-pasted and adjusted from ombi (especially on web), so maybe this can be merged in the future. Also, profile names are url-escaped like announcement template names were not too long ago. API client has "LogRequestBodies" option which just dumps the request body when enabled (useful for recreating reqs in the jellyseerr swagger UI). User.Name() helper returns a name from all three possible values in the struct.	2024-07-30 16:44:46 +01:00
Harvey Tindall	7b9cdf385a	jellyseerr: add notifications related methods ... similar in style to User, with Notifications/NotificationsTemplate, and named fields for modifying discord and telegram IDs, and two modify methods.	2024-07-29 17:58:42 +01:00
Harvey Tindall	73e985c45c	jellyseerr: add user modification methods ... addded permissions get/set before realizing it already comes as part of the User object. Split User attributes that will be templated into UserTemplate struct, which User inherits. ApplyTemplateToUser takes a UserTemplate, while ModifyUser takes a plain map with some typed fields (display name and email, for now).	2024-07-29 17:36:29 +01:00
Harvey Tindall	9c34192b4f	jellyseerr: start API client ... Currently uses an API key (Seems simpler for the user than importing the jfa-go user and granting perms). Strategy as follows: * MustGetUser(jfID) function checks the cache for user, if not, calls Jellyseerr's importer passing jfID. From either, the user object is returned, which (in later commits) can be used to update the user's email (and potentially other info). My API key is in there rn but its for a local testing instance, who cares.	2024-07-29 16:46:37 +01:00