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
euclid_wasm is a dependency of hyperswitch dashboard which includes list of connectors, PMs, and other related structs and enums. This also includes payout related stuff which is enabled under payouts feature. However, the feature payouts itself is missing from euclid_wasm crate. This needs to be added in the crate.
Expected Behavior
To be able to include payout related definitions in euclid_wasm in the final target if the feature was enabled.
Actual Behavior
Payout related definitions are not included in wasm target.
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
Go to '...'
Click on '....'
Scroll down to '....'
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.
If not (or if building/running locally), please provide the following details:
Operating System or Linux distribution:
Rust version (output of rustc --version): ``
App version (output of cargo r --features vergen -- --version): ``
Have you spent some time checking if this bug has been raised before?
Bug Description
euclid_wasm
is a dependency of hyperswitch dashboard which includes list of connectors, PMs, and other related structs and enums. This also includes payout related stuff which is enabled underpayouts
feature. However, the featurepayouts
itself is missing fromeuclid_wasm
crate. This needs to be added in the crate.Expected Behavior
To be able to include payout related definitions in
euclid_wasm
in the final target if the feature was enabled.Actual Behavior
Payout related definitions are not included in wasm target.
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the
x-request-id
response header to help us debug your issue.If not (or if building/running locally), please provide the following details:
rustc --version
): ``cargo r --features vergen -- --version
): ``Have you spent some time checking if this bug has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: