{"push_id":907725593,"size":1,"distinct_size":1,"ref":"refs/heads/javascript-refactor","head":"3cdaccfaf7d12674a6c1b6f890dd919ac4e2e836","before":"e774cd1c82d375641f5fe999403ead47d4475e6e","commits":[{"sha":"3cdaccfaf7d12674a6c1b6f890dd919ac4e2e836","author":{"email":"d8f4ce6defa97e790825a29b007bb23bd2338643@gmail.com","name":"Oliver Hamlet"},"message":"Rewrite filters.js, and related plugin.js refactoring\n\nfilters.js now only exports an object that can be used to track filter\nstate, and contains functions for filtering using\nArray.prototype.filter(). As a utility class, it gets tested during\nthe new plugin tests.\n\nPluginCardContent is a new class for the data that gets displayed on\nthe front of plugin cards. It uses the filters to decide what is\nvisible and also converts the message data structure into something\na little simpler.\n\nPlugin.modPriority and Plugin.isGlobalPriority have been renamed to\nPlugin.priority and Plugin.isPriorityGlobal as they are more\nsensible names.\n\nI've also moved the filter state memory functions out of filters.js\nas they're more settings-related. I've also moved the conflicting\nplugins CEF callback and the filter application function out,\nbecause they were to complex/tightly coupled to other components\nto stay in there.\n\nI expect this breaks code that Plugin and the filters are used in.\nThe filters.hiddenPluginNo and filters.hiddenMessageNo have not\nyet been re-implemented and are currently missing. Given the\ncomplexity of the filtering, I'm thinking to just calculate their\nvalues at the end of a filter's event handler rather than tracking\ntheir state.","distinct":true,"url":"https://api.github.com/repos/loot/loot/commits/3cdaccfaf7d12674a6c1b6f890dd919ac4e2e836"}]}