Ole-Morten Duesund
e8428de775
Vite + TypeScript PWA that mirrors the Android app's core features: - Pre-processed shelter data (build-time UTM33N→WGS84 conversion) - Leaflet map with shelter markers, user location, and offline tiles - Canvas compass arrow (ported from DirectionArrowView.kt) - IndexedDB shelter cache with 7-day staleness check - Service worker with CacheFirst tiles and precached app shell - i18n for en, nb, nn (ported from Android strings.xml) - iOS/Android compass handling with low-pass filter - Respects user map interaction (no auto-snap on pan/zoom) - Build revision cache-breaker for reliable SW updates Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
30 lines
No EOL
1.2 KiB
JavaScript
30 lines
No EOL
1.2 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.escape = void 0;
|
|
/**
|
|
* Escape all magic characters in a glob pattern.
|
|
*
|
|
* If the {@link MinimatchOptions.windowsPathsNoEscape}
|
|
* option is used, then characters are escaped by wrapping in `[]`, because
|
|
* a magic character wrapped in a character class can only be satisfied by
|
|
* that exact character. In this mode, `\` is _not_ escaped, because it is
|
|
* not interpreted as a magic character, but instead as a path separator.
|
|
*
|
|
* If the {@link MinimatchOptions.magicalBraces} option is used,
|
|
* then braces (`{` and `}`) will be escaped.
|
|
*/
|
|
const escape = (s, { windowsPathsNoEscape = false, magicalBraces = false, } = {}) => {
|
|
// don't need to escape +@! because we escape the parens
|
|
// that make those magic, and escaping ! as [!] isn't valid,
|
|
// because [!]] is a valid glob class meaning not ']'.
|
|
if (magicalBraces) {
|
|
return windowsPathsNoEscape ?
|
|
s.replace(/[?*()[\]{}]/g, '[$&]')
|
|
: s.replace(/[?*()[\]\\{}]/g, '\\$&');
|
|
}
|
|
return windowsPathsNoEscape ?
|
|
s.replace(/[?*()[\]]/g, '[$&]')
|
|
: s.replace(/[?*()[\]\\]/g, '\\$&');
|
|
};
|
|
exports.escape = escape;
|
|
//# sourceMappingURL=escape.js.map
|