You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like we the API framework is not able to generate bad request response when posting wrong\bad JSON
Metadata:
EndpointMetadata.post(ROUTE)
.operationId("registerValidator")
.summary(
"Provide beacon node with registrations for the given validators to the external builder network.")
.description(
"Prepares the beacon node for engaging with external builders."
+ " The information will be sent by the beacon node to the builder network."
+ " It is expected that the validator client will send this information periodically"
+ " to ensure the beacon node has correct and timely registration information"
+ " to provide to builders. The validator client should not sign blinded beacon"
+ " blocks that do not adhere to their latest fee recipient and gas limit preferences.")
.tags(TAG_VALIDATOR, TAG_VALIDATOR_REQUIRED)
.requestBodyType(
SIGNED_VALIDATOR_REGISTRATIONS_SCHEMA.getJsonTypeDefinition(),
SIGNED_VALIDATOR_REGISTRATIONS_SCHEMA::sszDeserialize)
.response(SC_OK, "Registration information has been received.")
.withBadRequestResponse(
Optional.of(
"The request could not be processed, check the response for more information."))
.build());
- added integration test for PostRegisterValidatorTest, showing invalid data coming in, and a resulting 400.
- had to add a default exception handler for `JsonProcessingException`.
fixesConsensys#5571
Signed-off-by: Paul Harris <[email protected]>
- added integration test for PostRegisterValidatorTest, showing invalid data coming in, and a resulting 400.
- had to add a default exception handler for `JsonProcessingException`.
fixes#5571
Signed-off-by: Paul Harris <[email protected]>
Seems like we the API framework is not able to generate bad request response when posting wrong\bad JSON
Metadata:
Integration test:
The text was updated successfully, but these errors were encountered: