Open vemv opened 9 months ago
Hi @vemv,
Thank you so much for your kind feedback and the idea. In addition to attaching the docstrings and discoverability of the available options, I like it because:
My thoughts:
stevia/from
, so some form of generation from a single source would be ideal.{::from "The FROM instruction..."}
instead of spec, so Show Usages / Peek References would still find it but this is not as nice as jumping to definition.dockerfile.stevia
namespace would be generated and the format
implementation moved to dockerfile.stevia.format
namespace.::stevia/copy.link
for the --link
flag of COPY
.Time-permitting, I will think about implementing this, and of course more feedback or PR(s) would be welcomed. Thank you again for the comment and have a good weekend!
Paweł
Hi @PawelStroinski !
Very nice lib - I'm looking forward to use it the next time the need pops up.
It occurred to me that if each keyword had a ns-qualified equivalent, one could:
::stevia/<TAB>
and see what's thereIn practice, this an agnostic pattern that works:
...the
#_
is a minimalistic way to add a docstring even when it's not supported currently at Spec level.A couple of tools that can work with that:
cider-find-keyword
to jump to the 'definition' of the keywordwdyt?
Thanks - V