There's no reason to have an extra language involved in KLibs when it isn't needed, and the user_queries.json file is a bit confusing (and hard to document) as a result of being a JSON file. As an alternative, user queries should be able to be defined using Python objects, which have the benefit of being easily usable outside the context of demographics collection.
There's no reason to have an extra language involved in KLibs when it isn't needed, and the
user_queries.jsonfile is a bit confusing (and hard to document) as a result of being a JSON file. As an alternative, user queries should be able to be defined using Python objects, which have the benefit of being easily usable outside the context of demographics collection.