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

Data coersion #24

Closed
iamvery opened this issue May 24, 2016 · 1 comment
Closed

Data coersion #24

iamvery opened this issue May 24, 2016 · 1 comment

Comments

@iamvery
Copy link
Owner

iamvery commented May 24, 2016

All the examples given of ratchet show raw data as a static map. This is not realistic. We need to provide some functionality that helps map user's data into the form ratchet expects...

@iamvery
Copy link
Owner Author

iamvery commented Sep 24, 2016

This is probably addressed by #46. It's not really a lot of functionality, but the basic idea is:

Data.new
|> Data.scope(:foo, "bar")
# => %{foo: "bar"}

It would be interesting to see if a macro could be developed to save the Map functions called at runtime.

@iamvery iamvery closed this as completed Sep 24, 2016
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

1 participant