[02:06] <blr> wgrant: trying to reason through something relating to a RefVocabulary - existing vocabularies with restrictions are typically providedBy() context, but in this case the target repository is set clientside.
[02:12] <wgrant> blr: Yeah, the dependency is somewhat inconvenient.
[02:12] <wgrant> It may be best to implement it purely client-side.
[02:14] <wgrant> That is, there should be a RefVocabulary on IGitRepositoy. You may not be able to fit that into the normal form infrastructure, but your JS will be able to see the currently chosen repo and construct the URL appropriately.
[02:15] <blr> ok, that makes sense. thanks
[04:09] <wgrant> blr: Have you worked out a way to do it?
[04:09] <wgrant> blr: I can't immediately think of any examples on forms, but the "Link a related branch" JS widget on BugTask:+index does some special stuff.
[04:29] <blr> wgrant: hmm possibly, will have a look at the bugtask js, thanks
[04:30] <wgrant> IIRC it manually constructs the vocab URL and even triggers a search immediately in some scenarios.
=== Spads_ is now known as Spads
=== ev_ is now known as ev
=== broder_ is now known as broder
=== igitoor_ is now known as igitoor
=== G_ is now known as G