feat(torii): update model members and table when same model is registered again
fixes DOJ-120, #1268
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 69.09%. Comparing base (
8bfd5ad) to head (3388030). Report is 28 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #1634 +/- ##
=======================================
Coverage 69.09% 69.09%
=======================================
Files 265 265
Lines 26859 26859
=======================================
Hits 18559 18559
Misses 8300 8300
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Maybe this is a temp fix? But I think one issue is if we update an existing model with a new member, all records would be lost for that model in the db. However, the record state onchain still exists. We may need to do a more sophisticated db migration based on what changes are made to an existing model (ie add/remove/update columns)
Will close if favor of better migration generated on the model changes. @Larkooo please feel free to re-open if this is still needed anyway. 👍