Mitar
Mitar
You have `BlazeComponent.components` which contains all the components. See [here](https://github.com/peerlibrary/meteor-base-component/blob/master/lib.coffee#L121). Which variables are you thinking about? The `ReactiveField` you attach in `onCreated`?
See [explanation here](https://github.com/peerlibrary/meteor-base-component/blob/master/lib.coffee#L39). So you can use that constant instead, so `BlazeComponent.components[ComponentsNamespace.COMPONENTS_FIELD]`.
Feel free to create a pull request with static method on `ComponentsNamespace` to return all components inside a namespace, and another for all sub-namespaces. So feel free to organize that...
But are attributes dynamically added after construction of the component? So, there are multiple things we ca be talking here: - arguments you pass with `{{> component args }}` -...
BTW, do you know of: https://github.com/peerlibrary/meteor-blaze-components-explorer My attempt at creating a global component list: http://components-explorer.meteorapp.com/ I never had time to really do it, but my idea was to: - have...
> As we are going this far, why not list the event binding? (We are defining events on js) Isn't this internal to the component? User of a component should...
> I can look for helpers, arguments, reactive fields and generate a clean array of objects as a result I am not sure how you can really do that? They...
> I'm pretty sure that extending this functions I can get reactive fields, for example. Try. :-) As I said, reading the prototype is easy, reading things you attach onto...
I think `getVars` is very fragile. Also, your function works only in development mode, when code is not minimized. Moreover, you should probably be using inline event handler instead of...