The use of a separate slice to keep track of login status adds redundancy to the application, as the login state is already managed by the firebase library. This has led to issues such as #74, which relied on the firebase library to keep track of the login state. As a result, the POST payload included the "logged-in" user's ID when none was expected for a found item submission.
Suggestion:
To depend on login state by firebase, which requires #61 to be addressed first.
The use of a separate slice to keep track of login status adds redundancy to the application, as the login state is already managed by the firebase library. This has led to issues such as #74, which relied on the firebase library to keep track of the login state. As a result, the POST payload included the "logged-in" user's ID when none was expected for a found item submission.
Suggestion:
To depend on login state by firebase, which requires #61 to be addressed first.