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

Custom types #180

Merged
merged 8 commits into from
Jan 28, 2016
Merged

Custom types #180

merged 8 commits into from
Jan 28, 2016

Conversation

dmskr
Copy link

@dmskr dmskr commented Jan 26, 2016

No description provided.


var customHooks = _.flatten(_.map(_.keys(customTypes), function(key) {
// Modify a names of the hooks to include field name they applied to
_.each(customTypes[key].hooks, function(whenHooks, when) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it expect a structure like this? It kind of doesn't follow semantics of hooks?

{before: {
   write:  {
    fn: function(){}
   }
 }
}`

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it does. But not sure what you meant by "It kind of doesn't follow semantics of hooks?". Can you pls extend the statement

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, think i got it. In design doc these hooks were passed through as properties of options, but chaining is probably even better.

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

Successfully merging this pull request may close these issues.

2 participants