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

Define source_tx_type as an enum instead of a string #2082

Open
davidyuk opened this issue Feb 3, 2025 · 0 comments · May be fixed by #2091
Open

Define source_tx_type as an enum instead of a string #2082

davidyuk opened this issue Feb 3, 2025 · 0 comments · May be fixed by #2091
Assignees

Comments

@davidyuk
Copy link
Member

davidyuk commented Feb 3, 2025

Currently, in multiple places, it is defined as

source_tx_type:
  type: string
  example: NameTransferTx

https://github.com/aeternity/ae_mdw/blob/e278d0c0b8723028193b74a9412932e2858f5f61/docs/swagger_v3/names.spec.yaml#L261-L263

would be good to list all possible values. So the developer can handle all possible cases on his side.

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

Successfully merging a pull request may close this issue.

2 participants