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 catstack bundle utility functions like lodash or micro-js/* #101

Open
ahdinosaur opened this issue Apr 25, 2016 · 2 comments
Open

Comments

@ahdinosaur
Copy link
Member

lodash/fp

/cc @iainkirkpatrick

@iainkirkpatrick
Copy link
Member

hmmm, immediate thoughts:

pros: currying is nice, it makes me want to write nicer, more modular functions. immutable operations sounds nice too though the docs don't really explain what that means.

cons: can't refer as easily to the main lodash docs for help, and the fp docs aren't as nice with examples etc. some custom args order for some functions?

wonder if it's worth figuring out how often we would actually _.curry with regular lodash, and if it's pretty often, then switch?

@ahdinosaur
Copy link
Member Author

regarding original issue: going to try using lodash/fp on %cobuy, will see how it goes.

however will refocus this issue on the question: should catstack bundle utility functions, either as an normal export or depject modules?

@ahdinosaur ahdinosaur changed the title use lodash/fp instead of lodash? should catstack bundle utility functions like lodash or micro-js/* Feb 21, 2017
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