wagtail/client
Karl Hobley 6ffdb0d9ec Set referer policy of upgrade notifcation to "strict-origin-when-cross-origin"
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
- Since Django 3.1, all Wagtail admin responses have been given a referer-policy: same-origin header. See: https://chipcullen.com/django-3-referrer-policy-change/
- #8560
2022-05-19 19:06:46 +10:00
..
.storybook Use stubs in storybook 2021-05-03 17:05:56 +01:00
scss Update move page breadcrumb 2022-01-19 22:22:40 +00:00
src Set referer policy of upgrade notifcation to "strict-origin-when-cross-origin" 2022-05-19 19:06:46 +10:00
tests Support changing which origin the integration tests are run on 2022-01-15 21:44:36 +10:00
README.md Refactor explorer code with tests using Jest 2017-05-13 23:53:10 +03:00
package-lock.json Feature/field comment frontend (#6530) 2021-04-20 18:25:30 +01:00
webpack.config.js Rename admin/expanding-formset.js (using kebab-case file) (#7833) 2022-01-15 01:00:02 +00:00

README.md

Wagtail client-side components

This library aims to give developers the ability to subclass and configure Wagtail's UI components.

Usage

npm install wagtail
import { Explorer } from 'wagtail';
// [...]
<Explorer />

Development

# From the project root, start the webpack + styles compilation.
npm run start

You will also need:

Releases

The front-end is bundled at the same time as the Wagtail project. This package also aims to be available separately on npm as wagtail.