| Commit message (Collapse) | Author | Age | Files |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It appears var() validation from https://github.com/eslint/css/pull/148
doesn't look if the variable have been defined in the sourced .css files,
yielding many false positive
68:30 error Can't validate with unknown variable '--bs-body-bg-rgb' css/no-invalid-properties
69:22 error Can't validate with unknown variable '--bs-modal-border-radius' css/no-invalid-properties
[…]
So we disable these rules for now. (According to the PR, property
values containing var() were skipped prior to v0.9.0.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We use usual integer comparison against the feature's timestamp
internally, so for relative filters we need to adjust boundaries at
midnight. The help text needs updating too if the modal is open and
the relative dialog checked.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason is that we want the different modules to produce side-effects
(to avoid creating functions and keeping references to it) and we
therefore need to control the order in which they are inlined during
`vite build`. Unfortunately this doesn't seem to be possible right now,
cf. https://github.com/storybookjs/storybook/issues/30768 .
This reverts commits 670bba058d83620abdb3e8db5fd4ea89dba08142,
05a018f27aba3a20fd581cb88daa8afbbd3407de and
0fc7bdd8bf374c36fa0ba27702d1fafed09277ac.
|
|
|
|
|
|
| |
This allows importing `map` in other modules, thereby eliminating the
need for creating and exporting functions that would be called only
once.
|
| |
|
|
|
|
|
|
| |
This avoids the following warning:
[vite] warning: rewrote […] to node_modules/[…] but was not an abolute path and was not handled by other plugins. This will lead to duplicated modules for the same path. To avoid duplicating modules, you should resolve to an absolute path.
|
|
|
|
|
| |
We might filter away the feature currently selected so it makes sense to
clear the feature list first.
|
| |
|
| |
|
| |
|
|
|
|
| |
To match the ordering from https://vbk.lansstyrelsen.se/ .
|
|
|
|
|
| |
In particular, fix a bug where not the entire height was used for the
popover body.
|
|
|
|
| |
We don't want to lint anything under ./dist/, for instance.
|
|
|
|
|
| |
In particular, make the definition object hierarchical and rename its
fields.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: https://eslint.org/docs/latest/rules/no-loss-of-precision
|
|
|
|
| |
And also fix `isVisible()` along the way.
|
| |
|
| |
|
| |
|
|
|
|
| |
To be used with `npm run lint`.
|
|
|
|
| |
Using `npm init @eslint/config@latest`.
|
|
|
|
|
|
| |
This rather large commit merely moves the object declaration into the
new file and adjusts the import declarations accordingly. This will
serve as basis for a future refactoring commit.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Cf. 231d64cbd14c2d1ccb6468dc9666d4433e39834c in tools.
|
|
|
|
|
| |
Right now this is only implemented for avverk, mrr and vbk as other
layers don't export the property.
|
|
|
|
|
| |
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
That simplifies the logic slightly.
|
| |
|
| |
|
| |
|
|
|
|
| |
Thereby making it easier to extend if needs be.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Replace `a === undefined || a === null` resp. `a !== undefined && a !== null` with
`a == null` resp. `a != null`.
See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Equality .
Relax also some `=== undefined` and `=== null` into `== null` when that
makes sense.
|
| |
|
|
|
|
|
| |
Also, don't define a projection for raster layers and let OL get it from
the source's metadata instead.
|
| |
|