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

A way to use 2 different transaction classes #50

Open
ShalitMonero opened this issue Mar 6, 2023 · 0 comments
Open

A way to use 2 different transaction classes #50

ShalitMonero opened this issue Mar 6, 2023 · 0 comments

Comments

@ShalitMonero
Copy link

ShalitMonero commented Mar 6, 2023

Please read this issue before to get context: #7
Here I propose a way to solve this issue by using a "facade" class that will include a way to use the functionality of both of the transaction classes. When creating the instance the user will have to select the type of class he would like to use, then he will be able to use only the functionality that is related to the transaction class type.

Here is the implementation of my proposed solution:
https://gist.github.com/ShalitMonero/3b40a5478f448f0d7efae9a5a7fe4a8e

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

No branches or pull requests

1 participant