Rakesh Emmadi 010a313988 Expose error caused by negative limit and offset values in the API response (#471) ... Previously, negative values for `offset` and `limit` input fields resulted in an internal error and not exposed in the API response. The reason is that these errors are raised from normalized_ast conversion after GraphQL validation. The validation will only check for the type, but not the value of the input fields. This Commit: - Introduces a utility function to lift any unexpected value internal error to external. - Use the function for `limit` and `offset` input field value coercion. V3_GIT_ORIGIN_REV_ID: a186eb89a836359427e58f7a847eab3e2f8fafa4		2024-04-18 06:35:38 +00:00
..
benches	NDC response size limit (#439)	2024-04-04 04:56:50 +00:00
bin/engine	Put human readable span name in display.name and add context (#464)	2024-04-15 14:58:26 +00:00
src	Expose error caused by negative limit and offset values in the API response (#471)	2024-04-18 06:35:38 +00:00
tests	Expose error caused by negative limit and offset values in the API response (#471)	2024-04-18 06:35:38 +00:00
build.rs	Move all crates into a folder (#355)	2024-03-19 18:07:14 +00:00
Cargo.toml	Bump strum from 0.25.0 to 0.26.2 (#424)	2024-04-15 09:56:34 +00:00