Figure out why Bed disappears from cache

[capndave]

Type

Bed disappears from cache.

Problem or To-Do

When running locally, go to the Garden page. Note that a Bed will appear in the cache. Click on a garden. That bed is gone from the cache. We need the bed to stay in cache so that we can use its info in the Bed component.

Additional Information

n/a

[paytonagreen]

Had my mom in town until this morning, so I was checked out of programming world. Have you had a chance to check this out? I can look into it to, let me know if you've found anything!

[capndave]

No big deal! I need more time to look into it. My folks are coming into town this weekend!

…

On Tue, May 4, 2021 at 9:44 AM Payton Green ***@***.***> wrote: Had my mom in town until this morning, so I was checked out of programming world. Have you had a chance to check this out? I can look into it to, let me know if you've found anything! — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#70 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTOOZJFGT3RDEVIHOIRPI3TMAB5TANCNFSM4363QKYA> .

[paytonagreen]

I'll look into it this afternoon and report back!

[paytonagreen]

So far:

• I removed the columns that don't exist on the backend yet from the two Bed Queries, i.e 'height', 'width' (this was giving me an error)
• I show the Bed remaining in cache in both the Gardens and individual Garden view with this setup.
• It does seem to disappear when entering into the individual bed view, but this is because we're not firing off any queries in the individual Bed view (other than GET_CURRENT_USER), as we don't have the Bed view wired up to the backend as of yet.

I plan on making an issue/working today and tomorrow on updating the Bed model on the backend to include the missing criteria and wiring up the frontend component to display/update the data correctly. I think by creating that issue we can close this one?