Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.26%. Comparing base (71b2bab) to head (213b3a5).
Report is 48 commits behind head on main.

@@            Coverage Diff             @@
##             main    #5120      +/-   ##
==========================================
- Coverage   78.26%   78.26%   -0.01%     
==========================================
  Files         339      339              
  Lines       15967    15985      +18     
  Branches     3693     3697       +4     
==========================================
+ Hits        12497    12511      +14     
- Misses       3470     3474       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I'd propose to keep the platform settings in local storage, reason being that clearing the account state on logout could pose problems to the login page (rendering platform setting dependent elements like the sign-up button).

There's nothing in there that could be considered sensitive and the data is not subject to change very often either

Sorry - I'm out of time to get this reviewed. Will need to pass over to someone else.

can you explain why we have two resetState calls, one as a mutation and another as an action? What am i missing?

Yes, in Vuex, all state changes must pass through mutations.

This ensures that state updates are synchronous and trackable (actions can contain async logic but must commit mutations to modify the state). Even though in this particular case the action doesn't contain async code, directly modifying the state outside mutations violates Vuex principles and may lead to unexpected behavior