Harry Waye b7c898d23e feat(correlation): load exclude properties from team settings (#6715) ... * feat(correlation): add team wide person property exclusion list This change just adds the exclusion list to the `Team` model and checks that it can be updated. Separately we can: 1. add interface for the Project page to display 2. pull and update this list from the funnels correlation page NOTE: We don't perform any validation on the structure, :fingerscrossed: this won't be an issue. Alternative would be to use ArrayField, but use of JSONField is consistent with other fields. * test(correlation): add test checking exclude properties pulled from team * feat(correlation): load exclude properties from team settings Previously we were loading exclude properties from local storage, so we would not be sharing the exclusion list between users. This change simply plugs the `excludePropertyNames` into the `teamLogic` for the purpose of persisting and loading the values. * use [teamLogic.actionTypes.loadCurrentTeamSuccess] * get tests passing * switch frontend to using `correlation_config` * refactor: use Team.correlation_config for persistence * add project settings for correlation * fix lint * ensure excluded properties are saved to project config * Add default excluded properties * format * make propertyCorrelations not null * ensure excluded property names config is unique * rename excludeProperty to excludePropertyFromProject * update var names * change to targetProperties * remove null special casing * update to filter client side on exclude from project clicked * update test name to reflect new functionality * fix tests		2021-11-02 11:12:13 +00:00
..
test	feat(correlation): load exclude properties from team settings (#6715)	2021-11-02 11:12:13 +00:00
__init__.py
authentication.py
debug_ch_queries.py
enterprise_event_definition.py
enterprise_property_definition.py
explicit_team_member.py
hooks.py	Purge PLUGIN_SERVER_ACTION_MATCHING flag (#6358)	2021-10-11 21:33:48 +02:00
license.py