Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should atoms in toucan.hydrate flushed after defmodel? #34

Open
DogLooksGood opened this issue Mar 29, 2018 · 2 comments
Open

Should atoms in toucan.hydrate flushed after defmodel? #34

DogLooksGood opened this issue Mar 29, 2018 · 2 comments

Comments

@DogLooksGood
Copy link

When we change models, we may change hydration-keys, this change will not work unless we reload toucan.hydrate namespace. This looks inconvenient in development.

Since automagic-batched-hydration-key->model and automagic-batched-hydration-keys are delays, why not reload them after each time we call defmodel? maybe there's a better way for this?

@DogLooksGood DogLooksGood changed the title Should atoms in toucan.hydrate flushed after defmodel Should atoms in toucan.hydrate flushed after defmodel? Mar 29, 2018
@camsaul
Copy link
Member

camsaul commented May 16, 2018

PR #27 is close to what you want.

I'm hoping to get some tests in that PR so we can merge it in the near future

@camsaul
Copy link
Member

camsaul commented May 16, 2018

It is inconvenient but I think maybe doing (require 'toucan.hydrate :reload) in the REPL will at least let you continue working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants