hydra-processor: `db.save()` fails when there are cascaded saves due to null warthog fields.
Open
@dzhelezov is already working on this.
Since May 28, 2021.
bug
highest-prio-feature
hydra-cli
low-prio
- Dominant language
- TypeScript
- Stars
- 50
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Related: https://github.com/Joystream/hydra/issues/283
DatabaseManager.save() checks if the required warthog fields are set, and if not, populates with some fake data. However, it still fails when the passed entity has some related entity so the save operation is cascaded. Then the required fields are not set and the mapping fails.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.