From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Filip Schauer <f.schauer@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager v2 0/2] ui: storage oci pull: optimize and cleanup reference regex
Date: Thu, 11 Dec 2025 15:23:11 +0100 [thread overview]
Message-ID: <176546279552.187736.15722520165979478484.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251119135323.102447-1-f.schauer@proxmox.com>
On Wed, 19 Nov 2025 14:52:27 +0100, Filip Schauer wrote:
> Changed in v2:
> * remove unnecessary backslashes from regex ("\\/" becomes "/")
> * ran `make tidy`
>
> Filip Schauer (2):
> ui: storage oci pull: optimize reference regex
> ui: storage oci pull: split up long one-line regex
>
> [...]
Applied, thanks!
But maybe it would be more readable by using (string) variables for
the parts and re-use them where applicable when concatenating the full
string for the expression. Or is there a better way to build regexes
in JavaScript from smaller parts?
E.g. '[a-zA-Z\\d](?:[a-zA-Z\\d-]*[a-zA-Z\\d])?' could be a variable
and '[a-z\\d]+(?:(?:[._]|__|-+)[a-z\\d]+)*' could be one, both being
used twice if I'm not misreading it. And more could make sense like
'\\w[\\w.-]{0,127}' just to give that part a name too when
constructing the full regex.
[1/2] ui: storage oci pull: optimize reference regex
commit: 9fe9aa05f70cdaf98fa0c51d233125beb0467f2c
[2/2] ui: storage oci pull: split up long one-line regex
commit: d336324550daadb28f4fedbd8f05dbcb53427cc2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-11 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 13:52 [pve-devel] " Filip Schauer
2025-11-19 13:52 ` [pve-devel] [PATCH manager v2 1/2] ui: storage oci pull: optimize " Filip Schauer
2025-11-19 13:52 ` [pve-devel] [PATCH manager v2 2/2] ui: storage oci pull: split up long one-line regex Filip Schauer
2025-12-11 14:23 ` Fiona Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176546279552.187736.15722520165979478484.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox