CHANGELOG.md

# 0.3.4

- Improve duplicate-header errors display
- Upgrade to validata-core 0.5.4

# 0.3.3

- Adjustments in validation report display
- Upgrade to validata-core 0.5.3

# 0.3.2

- Upgrade to validata-core 0.5.2

# 0.3.1

- Upgrade to validata-core 0.5.1

# 0.3.0

- Repair tabular file structure prior to look for value errors

# 0.2.22

- Fix crash on home page if non existant repo

## 0.2.21

- Fix https://git.opendatafrance.net/validata/validata-ui/issues/64 (commonmark to HTML conversion)

## 0.2.20

- home page : allow HTML description for section

## 0.2.18

- better catalog error handling
- fix schema order in home page selects

## 0.2.15

- Catalog description on home page

## 0.2.11

- Sticky footer
- Fix crash on uploaded file validation

## 0.2.7

Technical changes:

- Replace Flask-Matomo by a client-side JavaScript function
- Remove configuration variable `MATOMO_AUTH_TOKEN`

## 0.2.6

Technical changes:

- Fix PDF report generation

## 0.2.4

New features for users:

- Render Markdown links table header, in the table that shows validation errors
- Ease clicking on links in popups, in the table that shows validation errors

## 0.2.2

Non-breaking changes:

- Don't fail if error loading catalog

## 0.2.1

Non-breaking changes:

- display version number in footer

## 0.2.0

New features for users:

- validate a tabular file (e.g. CSV) against a schema given by URL
- allow configuring homepage sections and blocks with a JSON config file (see `HOMEPAGE_CONFIG` environment variable in `.env`)
- allow validating against previous versions of schemas

Breaking changes:

- URLs changed because of schema version support

Non-breaking changes:

- UI now requests `validata-api` service to do the validation, and does not depend on `validata-core` anymore
- a Dockerfile has been added
- a Continuous Integration pipeline has been added
  - the Docker image is rebuilt for each release
  - the Python package is uploaded to [PyPI](https://pypi.org/) for each release

## 0.1.0

Non-breaking changes:

- Display badge in report page (optional, see `BADGE_CONFIG_URL` in `.env.example`)