From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v2] ui: DirEdit: LVMEdit: add hint when to enable shared
Date: Tue, 10 Oct 2023 16:31:03 +0200 [thread overview]
Message-ID: <906899cc-7583-4ec3-8149-44609f4d6e14@proxmox.com> (raw)
In-Reply-To: <2b5d69b7-24e5-409d-8781-30ca2914c800@proxmox.com>
Am 10/10/2023 um 15:19 schrieb Aaron Lauterer:
>>>
>>>
>>> diff --git a/www/manager6/storage/DirEdit.js b/www/manager6/storage/DirEdit.js
>>> index 7e9ec44d..8469a7c3 100644
>>> --- a/www/manager6/storage/DirEdit.js
>>> +++ b/www/manager6/storage/DirEdit.js
>>> @@ -30,6 +30,10 @@ Ext.define('PVE.storage.DirInputPanel', {
>>> name: 'shared',
>>> uncheckedValue: 0,
>>> fieldLabel: gettext('Shared'),
>>> + autoEl: {
>>> + tag: 'div',
>>> + 'data-qtip': gettext('Enable if the underlying file system is already shared between nodes.'),
>>> + }
>>
>> eslint complains about missing trailing comma
>
> hmm, when did that happen... now it does it too for me. Will send another version with it fixed.
We always had that rule enabled, it's a warning one, so `make install` will
only output the warning but continue, to make modify-build-test cycles easier,
but when building a debian package all the eslint warnings become errors.
There's a slight possibility that an earlier eslint had a false-negative here,
but tbh., I'd find that a bit odd as it's a relatively simple check.
prev parent reply other threads:[~2023-10-10 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 10:06 Aaron Lauterer
2023-10-10 13:06 ` Fiona Ebner
2023-10-10 13:19 ` Aaron Lauterer
2023-10-10 14: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=906899cc-7583-4ec3-8149-44609f4d6e14@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.