{"push_id":2615405291,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4ff5d3ae39c4d5bc821cd851bed94d3544eb99c6","before":"89cb4a4130c662945956761e525ab150f5c9f29b","commits":[{"sha":"4ff5d3ae39c4d5bc821cd851bed94d3544eb99c6","author":{"name":"dan sutton","email":"f4ed039ee2a17ba359ba4ab23f7735e8c88bb92f@gmail.com"},"message":"[Fix #2294] simplify stacktrace filter mechanism\n\npreviously there were two separate lists of positive and negative\nfilters and complicated logic spread throughout of how these\ninteracted. Now there is a single list that you can toggle flags on or\noff and their interaction is dictated inside of a single function\n`cider-stacktrace-apply-filters`. Since their interaction is here we\nno longer need to remember previous flags as they are just toggled on\nand off.\n\nPositive filters are 'all or 'project. These dictate that all frames\nshould be shown or only any frame from a project namespace should be\nshown, despite other filters. Also, these two cannot exist at the same\ntime, so we need to check which is most \"recent\". Since if 'project is\nselected, it hides all but project frames and if 'all is selected it\nmust show all. We do what was most recently selected in this case\nthen.\n\nSo the frame filtering is quite simply a list of tags you want to\nfilter by: '(java clj tooling repl dup project all). These are toggled\non and off as desired.","distinct":true,"url":"https://api.github.com/repos/clojure-emacs/cider/commits/4ff5d3ae39c4d5bc821cd851bed94d3544eb99c6"}]}
{"actor":{"display_login":"bbatsov"}}