Fork me on GitHub
#calva
<
2020-02-15
>
il-tmfv08:02:15

@pez Hi! I have two questions about Custom Connection Sequences. 1. According to the docs https://calva.readthedocs.io/en/latest/connect-sequences.html any custom seq will “override” built-in seqs, so they won’t appear. Do I need to add them in project’s workspace only then? B/c otherwise it will make it harder to do jack-in for other projects that can rely on built-in seqs. BTW, the link to built-ins is broken, the correct one - https://github.com/BetterThanTomorrow/calva/blob/master/src/nrepl/connectSequence.ts 2. I have a project that uses lein + legacy figwheel , I see that built-in seq doesn’t support build ids in it - https://github.com/BetterThanTomorrow/calva/blob/master/src/nrepl/connectSequence.ts#L133-L142. But other profiles have placeholders like %BUILD% & %BUILDS%. Can I somehow pass a build id? Because right now I have 2 almost identical custom seqs with different parts in ... (figwheel-sidecar.repl-api/start-figwheel! "here build-a or build-b") ... . I had tried to use menuSelections: { cljsLaunchBuilds: ["a", "b"] } with my custom seq, but didn’t see any prompt.

pez08:02:54

Hi! 1. Yes, this is meant to be used for workspace settings. 2. Currently there is no support for passing build id:s to legacy figwheel sequences. At least, I don't think so.