All of the main entry points in the rollcage APIs are created as a composition of def and partial, which fails to propagate metadata such as :doc and :arglists that could be used by IDEs to show contextual information while writing code.
As an example, here's what CIDER looks like when I type (cicleci.rollcage.core/notify |) (where | stands for the caret position):
As I tend to constantly forget the order of arguments to the various logging functions, I'd like to propagate metadata to those functions that (I suppose) are used by most people.
Earlier last December I hastily created #48 without reading the README first, which suggests an issue should be created before merge requests. Here I am, trying to fix such a procedural mistake :-)
All of the main entry points in the
rollcage
APIs are created as a composition ofdef
andpartial
, which fails to propagate metadata such as:doc
and:arglists
that could be used by IDEs to show contextual information while writing code.As an example, here's what CIDER looks like when I type
(cicleci.rollcage.core/notify |)
(where|
stands for the caret position):or an even simpler example:
But I expect almost no one to use the raw
notify
. At least here's what actually happens to me on a daily basis:As I tend to constantly forget the order of arguments to the various logging functions, I'd like to propagate metadata to those functions that (I suppose) are used by most people.
Earlier last December I hastily created #48 without reading the
README
first, which suggests an issue should be created before merge requests. Here I am, trying to fix such a procedural mistake :-)Thoughts?