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.

Sign up for GitHub

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

Jump to bottom

fix: use serde content for token enum #7

Merged
merged 1 commit into from
Apr 24, 2024
Merged

fix: use serde content for token enum #7

merged 1 commit into from
Apr 24, 2024

Commits on Apr 24, 2024

  1. fix: use serde content for token enum 

    BREAKING CHANGE:
json output is no longer like:
```json
{"token": "Ingredient", "name": "foo", "amount": "1", "unit": "gr"}
```
now:
```json
{"token": "Ingredient", "content": {"name": "foo", "amount": "1", "unit": "gr"}}
```
The problem is that serde was failing to serialize enum variants that contained a single string
    @woile
    woile committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    719c207 View commit details
    Browse the repository at this point in the history