Skip to content

Full NoAuth Path (saving after registration) results in history list page to not requery for history objects #48

@cpshaheen

Description

@cpshaheen

how we check to re-ask (get method) for those objects needs to be dynamic - (requery whenever history page is visited - only rerender if number of returned history objects mismatches existing number - which in the case of this bug would be 0 and thus always cause a rerender since the backend will return that one newly created set from the no auth flow)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions