diff --git a/CHANGELOG.md b/CHANGELOG.md index b770a373b..16fc6f501 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,9 @@ This changelog covers all three packages, as they are (for now) updated as a who - Add `Store.parseMetaTags` to load JSON-AD objects stored in the DOM. Speeds up initial page load by allowing server to set JSON-AD objects in the initial HTML response. - Move static assets around, align build with server and fix PWA #292 +- `store.createSubject` allows creating nested paths +- Add `useChildren` hook and `Store.getChildren` method +- Add `Store.postToServer` method, add `endpoints`, `import_json_ad_string` ## v0.35.0 diff --git a/data-browser/README.md b/data-browser/README.md index 034a54816..f76d05ecf 100644 --- a/data-browser/README.md +++ b/data-browser/README.md @@ -77,11 +77,11 @@ You can set the Agent on the `/app/agent` route. The tests are located in `tests` and have `.spec` in their filename. They use the PlayWright framework and run in the browser. -- make sure the data-browser server is running (`pnpm start`) at `http://localhost:8080` -- make sure an [`atomic-server`](https://crates.io/crates/atomic-server/) instance is running at `http://localhost` +- make sure the data-browser server is running (`pnpm start`) at `http://localhost:5173` +- make sure an [`atomic-server`](https://crates.io/crates/atomic-server/) instance is running at `http://localhost:9883` - make sure the `http://localhost/setup` invite has at least one available usage. You can set a higher amount [here](http://localhost/app/edit?subject=http%3A%2F%2Flocalhost%2Fsetup), or run `atomic-server --inititalize` to reset it to 1. -- Install the Playwright dependencies: `npx playwright install-deps` -- `pnpm test` launches the E2E tests (make sure the dev server is running at `http://localhost:8080`) +- Install the Playwright dependencies: `pnpm playwright-install` +- `pnpm test` launches the E2E tests (make sure the dev server is running at `http://localhost:5173`) - `pnpm test-debug` launches the E2E tests in debug mode (a window opens with debug tools) - `pnpm test-new` create new tests by clicking through the app - Use the `data-test` attribute in HTML elements to make playwright tests more maintainable (and prevent failing tests on changing translations) @@ -92,9 +92,8 @@ They use the PlayWright framework and run in the browser. GitHub Action / Workflow is used for: - Linting (ESlint) -- Testing (in the browser using `playwright`, using an `atomic-server` docker image) - Building -- Deploying JS build artefacts & assets to GH pages (note that `atomic-server` hosts the JS assets by itself) +- Testing (in the browser using `playwright`, using an `atomic-server` docker image) ## Contribute diff --git a/data-browser/index.html b/data-browser/index.html index 83f6c9e67..48cc22277 100644 --- a/data-browser/index.html +++ b/data-browser/index.html @@ -34,6 +34,8 @@ + +
diff --git a/data-browser/src/components/ClassDetail.tsx b/data-browser/src/components/ClassDetail.tsx index 452767d61..bf4a29f66 100644 --- a/data-browser/src/components/ClassDetail.tsx +++ b/data-browser/src/components/ClassDetail.tsx @@ -2,6 +2,7 @@ import React from 'react'; import { properties, Resource, useString } from '@tomic/react'; import { ResourceInline } from '../views/ResourceInline'; import { Detail } from './Detail'; +import { getIconForClass } from '../views/FolderPage/iconMap'; type Props = { resource: Resource; @@ -15,8 +16,11 @@ export function ClassDetail({ resource }: Props): JSX.Element {
The back-end of this app is{' '}
-
The easiest way to run an{' '}
- Run your own server