-
Notifications
You must be signed in to change notification settings - Fork 6
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
Isolayer stuff should be in its own component #138
Comments
agreed! i can't quite remember why it ended up there. i think there was a reason why it was more straightforward, but it'd be worth sorting that out and refactoring so that it is easy to separate out the logic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the isolayer logic lives inside some of the base component code, and we should probably move it to a subcomponent. Possibly an isolayer component with a data reference to the block collection.
The text was updated successfully, but these errors were encountered: