4 Commits

Author	SHA1	Message	Date
Lukas Wagner	eff279e771	ui: sync job: fix error if local namespace is selected first ... When creating a new sync job and a local namespace is configured without setting a remote first, the createMaxPrefixLength was passed an array instead of a string/undefined/null, which triggered a 'ns2.match is not a funtion exception', making the UI glitchy afterwards. Fixed by explicitly checking for a string. Verified that the other user of NamespaceMaxDepthReduced, the prune job edit window, does not break after the change. Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>	2024-04-25 11:50:02 +02:00
Thomas Lamprecht	f07e660153	ui: move max NS prefix length logic to reduced max-depth selector ... for better re-usability in the future and it felt a bit odd to have such specific logic in the sync job edit directly Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>	2022-05-13 13:15:02 +02:00
Fabian Grünbichler	9dde8cd625	ui: sync: add reduced max-depth selector ... that allows setting the limit based on sync namespace prefix lengths. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>	2022-05-13 12:20:29 +02:00
Thomas Lamprecht	ad7741a294	ui: verify job: make namespace and max-depth aware ... Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>	2022-05-12 09:33:50 +02:00