Andrew Pett
Andrew Pett
Also appears to not work with `Phoenix.View`.
Thanks for the reply Holden. The OWASP page is good 👍 - Glad both pages mention that this is security by obscurity. Protecting introspection by authorization is a nicer middle...
Not sure how a violation of terms of service is relevant to you, the plugin author, unless you're violating those terms yourself or proxying requests for others. Glad to hear...
Looks like this duplicates #55
In this particular case, I am adding Boundary to an existing application where we'll iterate away some dirty xrefs. Unfortunately it means I can't promote this particular subboundary to top...
In this use case, there are many subcontexts, and also many modules in this particular `Subcontext` which make sense to be exported as part of a migration towards cleaner boundaries....
> > I had actually discovered this issue when trying to export like, > > ``` > > use Boundary, > > deps: [...], > > export: [ > >...
Any chance of this or another solution making it's way in? I've just hit my head up against this issue too.