public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Sterz <s.sterz@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v1 1/2] fix #4328: make help buttons in the markdown editor window work again
Date: Tue, 8 Nov 2022 16:31:10 +0100	[thread overview]
Message-ID: <407a5788-14e9-dfd8-e887-ecd000c7683d@proxmox.com> (raw)
In-Reply-To: <20221108150130.2415229-1-s.sterz@proxmox.com>

Am 08/11/2022 um 16:01 schrieb Stefan Sterz:
> when the `onlineHelp` of a component is defined in the widget toolkit
> `asciidoc-pve` can't pick up on that and `OnlineHelpInfo.js` won't
> contain the necessary keys. this patch sets `onlineHelp` in this
> package again to avoid that.
> 
> note: technically it would be enough to set this for one of the three
> usages of `pmxNotesView`, as then `asciidoc-pve` would add it to
> `OnlineHelpInfo.js` again. however, for consistency's sake i added it
> to all occurrences.
> 
> Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
> ---
> so this issue doesn't only affect the markdown notes, there are also
> other components affected by this. afict this includes:
> 
> * `proxmoxNodeNetworkView`: needs `sysadmin_network_configuration`,
>   which works because it is also set in `node/Config.js`, similar to
>   this fix.
> * several components related to tfa need `user_mgmt` which are all
>   currently broken, because that key isn't used at all in
>   `pve-manager`.
> 
> i think it would be nice to have a solution that allows setting such
> keys in the widget toolkit only, but that would require one of two
> changes:
> 
> 1. always add all possible keys to `OnlineHelpInfo.js`. to my
>    understanding, this is similar to how pbs currently creates its
>    `OnlineHelpInfo.js`
> 2. include the widget toolkit's javascript files in the input to
>    `asciidoc-pve`. however, i am unsure how we could do so elegantly.

 please go for 2., I'd do so by adding proxmox-widget-toolkit to the
 Build-Depends list in d/control and parse it from the file at
 /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js




      parent reply	other threads:[~2022-11-08 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 15:01 Stefan Sterz
2022-11-08 15:01 ` [pve-devel] [PATCH manager v1 2/2] ui: add javascript source to `OnlineHelpInfo.js` prerequisites Stefan Sterz
2022-11-08 15:28   ` [pve-devel] applied: " Thomas Lamprecht
2022-11-08 15:31 ` Thomas Lamprecht [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=407a5788-14e9-dfd8-e887-ecd000c7683d@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal