You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that, but I'm trying to make it easier to write smaller modules.
If your module is called the same thing as a single function then that's silly to type things such as mkdirp.mkdirp. and it's silly to have an instance when all it is is a utility. Therefor, my proposal is to use a closure response. It allows us to stick to CFCs but make things more elegant on usage.
Most of the core will be larger modules but for tiny things it might make sense to just return something other than this.
For instance, several components in the new FPM utility will return an emitter.
Trying to think outside the box now that CF supports more and could grow into a very mature little language.
This would provide a seemless interface for simple modules.
If a module has a single utility function then it could simply do
Allows for smoother requiring of the module as a function versus a redundant component.
The text was updated successfully, but these errors were encountered: