Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.2.0 #74

Merged
merged 2 commits into from
Nov 17, 2023
Merged

v0.2.0 #74

merged 2 commits into from
Nov 17, 2023

Conversation

jessicamcinchak
Copy link
Member

No description provided.

## [0.2.0] - 2023-11-17

### Breaking
- Renamed `result` to `preAssessment` and made optional, as applications from sources other than Planx are unlikely to provide this ([#66](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/66))
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is our first proper truly breaking change which bumps us up to v0.2.0, others agree? There's been a lot of "changing" types in these first weeks that I haven't classified as breaking yet because they began as optional, but that's not the case for result which was originally required.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep - this makes sense to me.

It's all a little abstract until third-parties (BOPS, Uniform) are really using this but it's good to follow best practice here.

@jessicamcinchak jessicamcinchak requested a review from a team November 17, 2023 11:41
Copy link
Contributor

@DafyddLlyr DafyddLlyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small typo / issue!

## [0.2.0] - 2023-11-17

### Breaking
- Renamed `result` to `preAssessment` and made optional, as applications from sources other than Planx are unlikely to provide this ([#66](https://github.com/theopensystemslab/digital-planning-data-schemas/pull/66))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep - this makes sense to me.

It's all a little abstract until third-parties (BOPS, Uniform) are really using this but it's good to follow best practice here.

Co-authored-by: Dafydd Llŷr Pearson <[email protected]>
@jessicamcinchak jessicamcinchak merged commit 976a23c into main Nov 17, 2023
@jessicamcinchak jessicamcinchak deleted the v0.2.0 branch November 17, 2023 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants