Stop failing build for unserializable assets
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
The current problem:
Currently in Stride if it can't serialize a field or property it fails the whole build with a messy stacktrace error.
Potential solution:
Can we make it so it shows a warning instead and just ignores that field/property?
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.
Research direction
No files, tests, or entry points are named. Reproduce a build with an unserializable asset field or property, then locate the asset serialization path and determine how the failure can become a warning while skipping only that member. Done means the build completes without the messy stack trace and the unserializable member is ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100