Chema Balsas

@BYK That sounds awesome!! I completely agree about building a proper plugin architecture outside the r2 package. We just wanted to have something working and get the ball rolling ;)...

Another important need for this, as we can see, is the possibility to register several plugins for the same valueMap functions. If functions receive context, then it's easy to just...

Hey @BYK, Have you been able to make any progress on this? Please, let us know if we could assist you in any way :)

Hi @BYK, thanks for letting me know. We applied the temporary solution to our fork and that's what we're using for now with good results. Sadly, I got sidetracked with...

Hey @peterflynn, I thought about this when I first implemented the search functionality, but couldn't do a lot more than that. I'd like to revisit this for the 0.5 milestone....

Hey guys, sorry this has been lingering for a while... I'm looking at the `@typedef` case... would it make sense to store those definitions and then show for example a...

But where should we put and show the `@typedef`s? It might make sense for the `@callback`s, since those will always related to some documented member, but `@typedef` is pretty much...

Also... isn't it possible that we could want to use some `@typedef` definition from a different module than the one we are currently in? Does that seem like a valid...

Sure... but would you want to jump there from the page you are? Wouldn't you prefer to see what it is in the context of the current module?

Maybe a table at the bottom with all used `@typedef`s in the module with their description...