From: Stefan Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v3 0/2] pve fix help buttons by accounting for keys in widget toolkit
Date: Mon, 14 Nov 2022 12:38:26 +0100 [thread overview]
Message-ID: <20221114113828.286081-1-s.sterz@proxmox.com> (raw)
this patch series fixes an issue where `onlineHelp` keys, that were
only used by components in the widget toolkit, were not properly
mapped to the corresponding anchors in the docs. this lead to
affected help buttons only showing an error message.
this series first fixes `pve-docs` by making `asciidoc-pve`
a bit less aggressiv in order to avoid keys that are set by cbind.
then it adds the toolkit as a build dependency to `pve-manager` and
scans the toolkit for keys there when building the front-end.
changes from v2, thanks @ Thomas Lamprecht:
* rebase to current master
* move to greedy regex
changes from v1, thanks @ Thomas Lamprecht:
* scan the widget toolkit too and not just components in
`pve-manager`
Stefan Sterz (1):
asciidoc-pve: disallow certain characters in onlineHelp keys
asciidoc-pve.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Stefan Sterz (1):
fix #4328: ui: add widget toolkit to dependencies of OnlineHelpInfo.js
debian/control | 1 +
www/manager6/Makefile | 6 ++++--
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2022-11-14 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 11:38 Stefan Sterz [this message]
2022-11-14 11:38 ` [pve-devel] [PATCH docs v3 1/2] asciidoc-pve: disallow certain characters in onlineHelp keys Stefan Sterz
2022-11-14 18:50 ` [pve-devel] applied: " Thomas Lamprecht
2022-11-14 11:38 ` [pve-devel] [PATCH manager v3 2/2] fix #4328: ui: add widget toolkit to dependencies of OnlineHelpInfo.js Stefan Sterz
2022-11-14 19:48 ` [pve-devel] applied: " Thomas Lamprecht
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=20221114113828.286081-1-s.sterz@proxmox.com \
--to=s.sterz@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