coilyco-flight-deck/eco-replay
1
0
Fork 0
Code Issues 9 Pull requests Projects Releases Packages Wiki Activity Actions

Improve body_json payload (currently empty) #7

New issue
Open
opened 2026-05-23 20:54:17 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-23 20:54:17 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-18T06:45:38Z - https://github.com/coilysiren/eco-replay/issues/1

Problem

The C# mod's ActionMapper.ToRow serializes each GameAction to a body_json column for inspection in the UI. Sampling the live Sirens DB right after first deploy shows every row's body is "{}".

Why: ShallowResolver.CreateProperty replaces User/ItemStack/WorldObject/Deed property values with their .Name, but the substitution mechanism (NameOnlyValueProvider) didn't fire on first run. Net effect: every property that would be serialized gets pruned or skipped, and we end up with {}.

Next steps

  • Decide whether the body should be: full reflective dump (a la Eco's own LiteDB serializer) or curated per-action-type (citizen, position, item-name, target) like Chronicler does.
  • The curated route is much more useful for grief-detection use cases. Most of Chronicler's reach comes from per-action-type extraction.

Out of scope

  • Web UI improvements past index.html table. That's its own issue.
_Originally filed by @coilysiren on 2026-05-18T06:45:38Z - [https://github.com/coilysiren/eco-replay/issues/1](https://github.com/coilysiren/eco-replay/issues/1)_ **Problem** The C# mod's `ActionMapper.ToRow` serializes each `GameAction` to a `body_json` column for inspection in the UI. Sampling the live Sirens DB right after first deploy shows every row's body is `"{}"`. **Why:** `ShallowResolver.CreateProperty` replaces `User`/`ItemStack`/`WorldObject`/`Deed` property values with their `.Name`, but the substitution mechanism (`NameOnlyValueProvider`) didn't fire on first run. Net effect: every property that would be serialized gets pruned or skipped, and we end up with `{}`. **Next steps** - Decide whether the body should be: full reflective dump (a la Eco's own LiteDB serializer) or curated per-action-type (citizen, position, item-name, target) like Chronicler does. - The curated route is much more useful for grief-detection use cases. Most of Chronicler's reach comes from per-action-type extraction. **Out of scope** - Web UI improvements past `index.html` table. That's its own issue.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/eco-replay#7
No description provided.