Gastón Fournier 37ce81a727 chore: re-use the same client schema for proxy (#3251) ... ## About the changes client-metrics-schema is less strict than proxy-metrics-schema because the former allows empty `instanceId` and also supports dates as timestamps as well as date-formatted strings. Using the same schema makes sense to reduce maintainability costs and it's less error-prone if we need to modify the schema because underlying the schema they both use the same code. The reasoning is that proxy metrics should align with our client metrics. Alternatively, we have new endpoints for edge metrics that will aggregate and bucket by client.  ## Discussion points Will we ever want to evolve proxy-metrics differently than client-metrics? I'm under the assumption that the answer is no		2023-03-03 16:36:23 +01:00
..
config	refactor: remove variants per environment feature flag (#3102)	2023-02-14 14:02:02 +00:00
e2e	chore: re-use the same client schema for proxy (#3251)	2023-03-03 16:36:23 +01:00
examples	fix: found an edge case exporting variants (#2900)	2023-01-13 14:55:57 +01:00
fixtures	feat: shared event emitter (#3241)	2023-03-02 09:52:19 +01:00
arbitraries.test.ts	feat(#1873/playground): Return detailed information on feature toggle evaluation (#1839)	2022-08-04 15:41:52 +02:00