Skip to content

Conversation

@LarsGast
Copy link
Contributor

@LarsGast LarsGast commented Jul 9, 2025

What does this do?

BREAKING CHANGE: dropped the race.starting_proficiencies, race.starting_proficiency_options, subrace.starting_proficiencies, subrace.language_options, and subrace.languages properties of all races and subraces in the database. Clients can instead find this data on the corresponding traits linked to each race or subrace.

How was it tested?

I ran the database + API project locally with Docker and called the endpoints of the various classes and subclasses. I also ran the unit and integration tests in the API project.

Is there a Github issue this is resolving?

Fixes #874

Did you update the docs in the API? Please link an associated PR if applicable.

I touched every reference of the properties in the API project. I took a look at the docs project, but couldn't fully find my way around the project to give a clear indication on if anything needed to change.
PR in API project

Here's a fun image for your troubles

One of my players designed their character after Clash of Clans P.E.K.K.A., and he dressed him up for the holidays last Christmas!
kerst pekka

@LarsGast LarsGast requested a review from bagelbits as a code owner July 9, 2025 18:05
@bagelbits bagelbits changed the title refactor(race/subrace): remove redundant data refactor(race/subrace)!: remove redundant data Jul 9, 2025
@bagelbits bagelbits merged commit 67261fb into 5e-bits:main Sep 4, 2025
10 checks passed
5e-bits-semantic-release-bot bot pushed a commit that referenced this pull request Sep 4, 2025
# [4.0.0](v3.26.1...v4.0.0) (2025-09-04)

* refactor(race/subrace)!: remove redundant data ([#875](#875)) ([67261fb](67261fb)), closes [#874](#874)

### BREAKING CHANGES

* dropped the `race.starting_proficiencies`,
`race.starting_proficiency_options`, `subrace.starting_proficiencies`,
`subrace.language_options`, and `subrace.languages` properties of all
races and subraces in the database. Clients can instead find this data
on the corresponding traits linked to each race or subrace.

## How was it tested?

I ran the database + API project locally with Docker and called the
endpoints of the various classes and subclasses. I also ran the unit and
integration tests in the API project.

## Is there a Github issue this is resolving?
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.

Remove redundant race and subrace data

2 participants