#392: stale data served to new user account (!625) · Merge requests · Pleroma / pleroma-fe · GitLab

Snippets Groups Projects

Merged #392: stale data served to new user account

Dave/pleroma-fe:issue-392-other-user-stale-data into develop

All threads resolved!

Merged Dave LiPuma requested to merge Dave/pleroma-fe:issue-392-other-user-stale-data into develop 6 years ago

All threads resolved!

stale data served to new user account

Closes #392 (closed)

Approval is optional

Activity

HJ @hj started a thread on an old version of the diff 6 years ago

Resolved 6 years ago by Dave LiPuma
Last reply by HJ 6 years ago

Dave LiPuma @Dave 6 years ago

Author Guest

@hj this defaultState was being exported and used in another place (unit testing). I just tried to remain the current structure as it is.

What do you think?

Dave LiPuma added 1 commit 6 years ago

added 1 commit

f5adb62e - #392 (closed): update defaultState into a function

Compare with previous version

HJ @hj 6 years ago

Maintainer

fix it everywhere

Dave LiPuma @Dave 6 years ago

Author Guest

Yeah, I just did. :)

Dave LiPuma resolved all discussions 6 years ago

resolved all discussions

HJ @hj started a thread on the diff 6 years ago

Resolved 6 years ago by HJ

Dave LiPuma added 1 commit 6 years ago

added 1 commit

bbe1821b - #392 (closed): update object.entries

Compare with previous version

HJ @hj started a thread on an old version of the diff 6 years ago

Resolved 6 years ago by Dave LiPuma

Dave LiPuma added 1 commit 6 years ago

added 1 commit

f3f9fbe3 - #392 (closed): clean up notification stopping section

Compare with previous version

Dave LiPuma resolved all discussions 6 years ago

resolved all discussions

Shpuld Shpludson mentioned in commit 6 years ago

mentioned in commit 09b0f6dd

Shpuld Shpludson merged 6 years ago

merged

Please register or sign in to reply