Andrei Prigorshnev d91456fd53 DEV: Ability to collect stats without exposing them via API (#23933) ... This adds the ability to collect stats without exposing them among other stats via API. The most important thing I wanted to achieve is to provide an API where stats are not exposed by default, and a developer has to explicitly specify that they should be exposed (`expose_via_api: true`). Implementing an opposite solution would be simpler, but that's less safe in terms of potential security issues. When working on this, I had to refactor the current solution. I would go even further with the refactoring, but the next steps seem to be going too far in changing the solution we have, and that would also take more time. Two things that can be improved in the future: 1. Data structures for holding stats can be further improved 2. Core stats are hard-coded in the About template (it's hard to fix it without correcting data structures first, see point 1): 63a0700d45/app/views/about/index.html.erb (L61-L101) The most significant refactorings are: 1. Introducing the `Stat` model 2. Aligning the way the core and the plugin stats' are registered		2023-11-10 00:44:05 +04:00
..
filter_manager.rb	DEV: Apply syntax_tree formatting to lib/*	2023-01-09 12:10:19 +00:00
filter.rb	DEV: Apply syntax_tree formatting to lib/*	2023-01-09 12:10:19 +00:00
instance.rb	DEV: Ability to collect stats without exposing them via API (#23933)	2023-11-10 00:44:05 +04:00
metadata.rb	DEV: Remove core plugins from plugin metadata file (#24070)	2023-10-23 15:26:59 -06:00