Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Swagger UI example provided in the /verify/create2 endpoint fails #89

Closed
acuarica opened this issue Dec 1, 2023 · 0 comments · Fixed by #164
Closed

The Swagger UI example provided in the /verify/create2 endpoint fails #89

acuarica opened this issue Dec 1, 2023 · 0 comments · Fixed by #164
Assignees

Comments

@acuarica
Copy link
Contributor

acuarica commented Dec 1, 2023

The default example provided in the Swagger UI for the /verify/create2 endpoint does not seem to have the proper schema. The field value should not appear. This is the default example provided

{
  "clientToken": "",
  "deployerAddress": "0x7dBA08Bdc233B28e2c99723c402Fc8F4e35AB55B",
  "salt": "0x00",
  "abiEncodedConstructorArguments": "00000000000000000000000006595656b93ce14834f0d22b7bbda4382d5ab51000000000000000000000000000000000000000000000000d8d726b7177a8000",
  "files": {
    "value": {
      "metadata.json": "{...}",
      "SimpleStorage.sol": "// file"
    }
  },
  "create2Address": "0x07880D44b0f7b75464ad18fc2b980049c40A8bc3"
}

The fields metadata.json and SimpleStorage.sol need to direct descendant of the files object, effectively removing the value field.

This is the response from the Swagger UI

image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant