Santhosh Janardhanan
de2d83092e
- Delete old Vite+Svelte frontend - Initialize new SvelteKit project with TypeScript - Configure Tailwind CSS v4 + DaisyUI - Implement JWT authentication with auto-refresh - Create login page with form validation (Zod) - Add protected route guards - Update Docker configuration for single-stage build - Add E2E tests with Playwright (6/11 passing) - Fix Svelte 5 reactivity with $state() runes Known issues: - 5 E2E tests failing (timing/async issues) - Token refresh implementation needs debugging - Validation error display timing
29 lines
1.2 KiB
JavaScript
29 lines
1.2 KiB
JavaScript
"use strict";
|
|
|
|
Object.defineProperty(exports, "__esModule", {
|
|
value: true
|
|
});
|
|
exports.isDomainSpecifiedByUser = isDomainSpecifiedByUser;
|
|
var _DataUtils = require("./DataUtils");
|
|
/**
|
|
* Takes a domain and user props to determine whether he provided the domain via props or if we need to calculate it.
|
|
* @param {AxisDomain} domain The potential domain from props
|
|
* @param {Boolean} allowDataOverflow from props
|
|
* @param {String} axisType from props
|
|
* @returns {Boolean} `true` if domain is specified by user
|
|
*/
|
|
function isDomainSpecifiedByUser(domain, allowDataOverflow, axisType) {
|
|
if (axisType === 'number' && allowDataOverflow === true && Array.isArray(domain)) {
|
|
var domainStart = domain === null || domain === void 0 ? void 0 : domain[0];
|
|
var domainEnd = domain === null || domain === void 0 ? void 0 : domain[1];
|
|
|
|
/*
|
|
* The `isNumber` check is needed because the user could also provide strings like "dataMin" via the domain props.
|
|
* In such case, we have to compute the domain from the data.
|
|
*/
|
|
if (!!domainStart && !!domainEnd && (0, _DataUtils.isNumber)(domainStart) && (0, _DataUtils.isNumber)(domainEnd)) {
|
|
return true;
|
|
}
|
|
}
|
|
return false;
|
|
} |