Menu ▾ ▴

#2118 macros madness in vaps

nextrelease
open
nobody
None
5
2026-02-28
2019-02-19
Jeremy Faden
No

I had a heck of a time figuring out what was wrong with a hand-edited vap, where ${} was used for a macro when %{} should have been. There needs to be better error feedback on this. Also there is no wiki page on using these macros, which are pretty flexible and could be used for spacecraft ID, for example.

Discussion

  • Jeremy Faden

    Jeremy Faden - 2026-02-27

    I was surprised and pleased when I saw that arbitrary macros worked in annotations, so you can have the annotation %{TODAY} and when you load the .vap with ...vap?TODAY=2026-02-27 it will plug in the value.

    This implies there is a namespace with some things removed, like %{PWD} and %{timerange}. Also I don't think all nodes of the .vap are resolved, and this needs to be documented. Further, there are things like %{CONTEXT} and %{TIMERANGE}.

     

    Last edit: Jeremy Faden 2026-02-28
MongoDB Logo MongoDB