You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a lot of places (e.g. apropos, the ns browser, etc) the users can see cider's namespaces and vars. We should filter those out (although we also need a way to not filter them while hacking on cider itself).
The text was updated successfully, but these errors were encountered:
I'd like to give this a try. Two approaches I can think of:
Put a filtering fn in cider somewhere, and a custom var which would contain the filtering prefixes.
Then, all functions, cider-sync-request:*, would filter out the configured prefixes.
Or, we could add another param to middleware requests, something like filter?, which would pass the prefixes and then the middleware would take care of this.
@expez Oh. Are you referring to the inlined-dependency fn? Guess we'll have to add support to optionally filter out cider.nrepl and refactor-nrepl in a similar way.
In a lot of places (e.g. apropos, the ns browser, etc) the users can see cider's namespaces and vars. We should filter those out (although we also need a way to not filter them while hacking on cider itself).
The text was updated successfully, but these errors were encountered: