Merge branch 'next' into update-redirect-file

Author: archiewood

.changeset/afraid-pumpkins-destroy.md

@@ -0,0 +1,5 @@
+---
+'@evidence-dev/core-components': patch
+---
+
+fixed US map abbreviaabbreviations string handling

.changeset/fuzzy-jokes-know.md

@@ -0,0 +1,5 @@
+---
+'@evidence-dev/core-components': patch
+---
+
+fixed legend false prop to respect strings

.changeset/itchy-buttons-promise.md

@@ -0,0 +1,5 @@
+---
+'@evidence-dev/core-components': patch
+---
+
+fixed deselection issue for start and end date

.changeset/spicy-grapes-decide.md

@@ -0,0 +1,5 @@
+---
+'@evidence-dev/core-components': patch
+---
+
+fixed slider delay with large min max value difference

.github/workflows/e2e.yml

@@ -5,25 +5,11 @@ on:
     branches: [main, next]
 
 jobs:
-  find-e2e-test-projects:
-    name: Find E2E Test Projects
-    runs-on: ubuntu-latest
-    outputs:
-      e2e-test-projects: ${{ steps.e2e-test-projects.outputs.e2e-test-projects }}
-    steps:
-      - uses: actions/checkout@v4
-
-      - id: e2e-test-projects
-        run: echo "e2e-test-projects=$(find e2e -maxdepth 1 -type d -printf "%f\n" | jq --raw-input --slurp --compact-output 'split("\n")[1:-1]')" >> ${GITHUB_OUTPUT}
-
   run-tests:
-    needs:
-      - find-e2e-test-projects
     timeout-minutes: 60
     strategy:
       fail-fast: false
       matrix:
-        project: ${{ fromJson(needs.find-e2e-test-projects.outputs.e2e-test-projects) }}
         os: [ubuntu-latest, macOS-latest, windows-latest]
         node-version: [18.13.0, 20, 22]
 
@@ -34,7 +20,7 @@ jobs:
           - isMain: false
             node-version: 20
 
-    name: e2e/${{ matrix.project }}/${{ matrix.os }}/node-${{ matrix.node-version}}
+    name: e2e/${{ matrix.os }}/node-${{ matrix.node-version}}
     runs-on: ${{ matrix.os }}
 
     steps:
@@ -60,28 +46,23 @@ jobs:
         run: pnpm playwright install --with-deps
 
       - name: Run setup
-        working-directory: ./e2e/${{ matrix.project }}
-        run: pnpm run --if-present setup
+        run: pnpm --filter "./e2e/*" run --if-present setup
 
       - name: Run sources
-        working-directory: ./e2e/${{ matrix.project }}
-        run: pnpm run sources
+        run: pnpm --filter "./e2e/*" run sources
 
       - name: Run dev mode tests
-        working-directory: ./e2e/${{ matrix.project }}
-        run: pnpm run test:dev
+        run: pnpm --filter "./e2e/*" --sequential run test:dev
 
       - name: Build
-        working-directory: ./e2e/${{ matrix.project }}
-        run: pnpm run build
+        run: pnpm --filter "./e2e/*" run build
 
       - name: Run preview mode tests
-        working-directory: ./e2e/${{ matrix.project }}
-        run: pnpm run test:preview
+        run: pnpm --filter "./e2e/*" --sequential run test:preview
 
       - name: Upload Playwright reports
         if: always()
         uses: actions/upload-artifact@v4
         with:
-          name: playwright-report__e2e_${{ matrix.project }}_${{ matrix.os }}_node-${{ matrix.node-version }}
-          path: e2e/${{ matrix.project }}/playwright-report
+          name: playwright-report__e2e_${{ matrix.os }}_node-${{ matrix.node-version }}
+          path: e2e/**/playwright-report

e2e/dev-server-startup/tests/tests.spec.js

@@ -25,7 +25,7 @@ test(`Should be timed appropriately`, async ({ page }) => {
 	await fs.rm(`test.log`, { force: true });
 
 	const procStartTime = performance.now();
-	const devServerProcess = child_process.spawn('npm', ['run', 'dev'], {
+	const devServerProcess = child_process.spawn('npm', ['run', 'dev', '--', '--port', '18000'], {
 		stdio: 'pipe',
 		shell: true,
 		env: {
@@ -67,7 +67,7 @@ test(`Should be timed appropriately`, async ({ page }) => {
 				// await new Promise((r) => setTimeout(r, 20000));
 				await fs.rm(`./.evidence/template/.evidence-queries`, { recursive: true, force: true });
 				const reqStartTime = performance.now();
-				await await fetch('http://localhost:3000?tag=the-real-request', {
+				await await fetch('http://localhost:18000?tag=the-real-request', {
 					headers: {
 						'User-Agent': 'Birds ARE real :)'
 					}
@@ -77,7 +77,7 @@ test(`Should be timed appropriately`, async ({ page }) => {
 				const firstRequestDur = reqFinishTime - reqStartTime;
 
 				const loadStartTime = performance.now();
-				await page.goto('http://localhost:3000');
+				await page.goto('http://localhost:18000');
 				await waitForPageToLoad(page);
 				await expect(page.getByText('Magic Text 🪄')).toBeVisible();
 				const lostFinishTime = performance.now();
@@ -118,6 +118,8 @@ test(`Should be timed appropriately`, async ({ page }) => {
 				devServerProcess.kill();
 			}
 		});
+	}).finally(() => {
+		if (!devServerProcess.killed) devServerProcess.kill();
 	});
 	expect([0, null]).toContain(exitCode);
 });

packages/extension/.vscodeignore

@@ -8,6 +8,7 @@ template/build/**
 template/.evidence/template/**
 data/**
 src/**
+!src/props_list.json
 
 docs/images/**
 

packages/extension/README.md

@@ -8,7 +8,7 @@
 
 This extension provides language support, Evidence project and dev server shortcut commands, and autocomplete for Evidence Markdown files.
 
-![Evidence Side-by-Side](docs/images/evidence-sidebyside.gif)
+![Evidence Side-by-Side](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-sidebyside.gif)
 
 ## Features
 
@@ -40,7 +40,7 @@ This extension also depends on [Svelte for VS Code](https://marketplace.visualst
 
 You can install the Evidence extension from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Evidence.evidence-vscode), or by searching for `Evidence` in the VS Code Extensions tab.
 
-![Evidence Extension Installation](docs/images/evidence-extension-install.png)
+![Evidence Extension Installation](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-extension-install.png)
 
 ## Getting Started
 
@@ -49,21 +49,21 @@ To get started with Evidence using VS Code locally, follow these steps:
 1. Open the command palette in VS Code (Cmd/Ctrl + Shift + P)
 2. Search for and click `New Evidence Project`
 3. Select an **empty** folder to create your Evidence project within<br><br>
-   ![Evidence Project Start](docs/images/evidence-new-project.gif)
+   ![Evidence Project Start](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-new-project.gif)
 
 4. Click the `Start Evidence` button to install all required dependencies and start the dev server, or use the commands detailed below in the `Commands` section<br><br>
-   ![Evidence Server Start](docs/images/evidence-server-start.gif)
+   ![Evidence Server Start](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-server-start.gif)
    <br><br> **Note:** The initial installation and server start can take up to 2 minutes depending on your computer. If you have issues with the startup time, you can use Codespaces (see next section).<br><br>
    At the end of this step, your browser will automatically open to your app preview, which will appear at `localhost:3000`
 
 5. We recommend putting VS Code and your browser side-by-side, like in the screenshot below. This will give you immediate development feedback on your app every time you save a markdown file.<br><br>
-   ![Evidence Side-by-Side](docs/images/evidence-sidebyside.gif)
+   ![Evidence Side-by-Side](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-sidebyside.gif)
 
 6. Make changes to your markdown files and save the file to see the changes reflected in your app preview
 
 7. Try the "slash commands" included with the extension by typing `/` - you will see a list of available viz and UI components from our library. Select a component to insert by hitting `Tab` or clicking on the component.<br><br>
    Once the component code has been inserted, you can hit `Tab` again to move through the inputs for a component and fill them in.<br><br>
-   ![Evidence Slash](docs/images/evidence-slash.gif)
+   ![Evidence Slash](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-slash.gif)
 
 ## Running Evidence in GitHub Codespaces
 
@@ -73,15 +73,15 @@ You can use the Evidence VS Code extension with [GitHub Codespaces](https://gith
 2. The Evidence extension will be installed automatically
 3. Click the `Start Evidence` button to install all required dependencies and start the dev server, or use the commands detailed below in the `Commands` section
 4. You will get a popup saying `Your application running on port 3000 is available`. Click to open in browser<br><br>
-   ![Running Evidence in GitHub Codespaces](docs/images/evidence-codespaces-server-start.png)
+   ![Running Evidence in GitHub Codespaces](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-codespaces-server-start.png)
 
 5. Make changes to your markdown files and **save the file** to see the changes reflected in your app preview
 
 6. After making changes to your project, click the `Source Control` icon in the left panel and commit your changes<br><br>
-   ![Make a change in Codespaces](docs/images/codespaces-make-change.png)
+   ![Make a change in Codespaces](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/codespaces-make-change.png)
 
 7. Click `Publish Branch` - this will prompt you to create a private or public repo for your Evidence project<br><br>
-   ![Publish repo in Codespaces](docs/images/codespaces-publish-repo.png)
+   ![Publish repo in Codespaces](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/codespaces-publish-repo.png)
 
 8. From here, you can continue to develop your project in Codespaces, or you can choose to clone your repo locally and work from there
 
@@ -91,7 +91,7 @@ The Evidence extension provides a number of custom VS Code shortcut commands for
 
 You can access the VS Code shortcut commands from the command palette (`Cmd/Ctrl+Shift+P`) by typing `Evidence` in the command search box:
 
-![Evidence Extension Commands](docs/images/evidence-commands.png)
+![Evidence Extension Commands](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-commands.png)
 
 | VS Code Command       | Title                      | Description                                                                                         | CLI Command                                                                      |
 | --------------------- | -------------------------- | --------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
@@ -113,7 +113,7 @@ Create [User or Workspace Settings](https://code.visualstudio.com/docs/getstarte
 
 Open Evidence extension Settings in VS Code by using the `Evidence: VS Code Extension Settings` command, or navigating to `File -> Preferences -> Settings` (`cmd/ctrl+,`) and searching for `Evidence` in the Settings search box.
 
-![Evidence Extension Settings](docs/images/evidence-extension-settings.png)
+![Evidence Extension Settings](https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-extension-settings.png)
 
 ### Available Settings
 
@@ -135,7 +135,7 @@ You can also reconfigure Evidence extension settings in `vscode/settings.json` w
 
 Edit your settings in `./vscode/settings.json` by opening the `Command Palette...` with `cmd/ctrl+shift+p`, searching for and selecting `Preferences: Open Workspace Settings (JSON)` command.
 
-![VS Code Settings JSON](https://raw.githubusercontent.com/evidence-dev/evidence-vscode/main/docs/images/evidence-vscode-settings-json.png?raw=true)
+![VS Code Settings JSON](https://raw.githubusercontent.com/evidence-dev/evidence-vscode/main/https://raw.githubusercontent.com/evidence-dev/evidence/next/packages/extension/docs/images/evidence-vscode-settings-json.png?raw=true)
 
 ### Evidence Settings
 

packages/extension/package.json

@@ -2,7 +2,7 @@
 	"name": "evidence-vscode",
 	"displayName": "Evidence",
 	"description": "Build polished data products with SQL and Markdown",
-	"version": "1.5.7",
+	"version": "1.5.9",
 	"private": true,
 	"engines": {
 		"vscode": "^1.52.0"

packages/ui/core-components/src/lib/atoms/inputs/date-input/DateInput.svelte

@@ -63,6 +63,14 @@
 
 	let currentDate = dateToYYYYMMDD(new Date());
 
+	let extraDayEndString;
+
+	$: if (endString && range) {
+		extraDayEndString = new Date(endString);
+		extraDayEndString.setDate(extraDayEndString.getDate() + 1);
+		extraDayEndString = formatDateString(extraDayEndString);
+	}
+
 	function onSelectedDateInputChange(selectedDateInput) {
 		if (selectedDateInput && (selectedDateInput.start || selectedDateInput.end) && range) {
 			$inputs[name] = {
@@ -103,6 +111,7 @@
 					{onSelectedDateInputChange}
 					start={startString}
 					end={endString}
+					{extraDayEndString}
 					loaded={loaded?.ready ?? true}
 					{presetRanges}
 					{defaultValue}