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

Wallet Provider backend's many names #344

Closed
rohe opened this issue Jul 3, 2024 · 3 comments · Fixed by #347
Closed

Wallet Provider backend's many names #344

rohe opened this issue Jul 3, 2024 · 3 comments · Fixed by #347

Comments

@rohe
Copy link
Contributor

rohe commented Jul 3, 2024

Some times called Wallet Provider some times Wallet Provider Backend.
I think they are one and the same entity so just choose one name and stay with it.

@cmarco0
Copy link
Contributor

cmarco0 commented Jul 3, 2024

In my opinion, distinguishing between "wallet provider" and "wallet provider backend" can be useful to clarify exactly which aspect of the service is being discussed.

If it makes sense, it would also be reasonable to include its definition in the Defined Terms chapter.

@rohe
Copy link
Contributor Author

rohe commented Jul 3, 2024

If it is as you say beneficial to use Wallet Provider and Wallet Provider Backend in different contexts then please do so.
But then as you say it should be made clear what the difference between them are in the Defined Terms chapter.

@peppelinux
Copy link
Member

@cmarco0 Wallet Provider is an entity and a defined term, Wallet Backend refers to the Wallet Provider's endpoints, therefore for the resolution of this issue all the occurrence of the term Wallet Backend should be renamed to Wallet Provider Backend

@grausof WDYT? ^

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

Successfully merging a pull request may close this issue.

5 participants