Closed wainola closed 5 months ago
@mpetrunic can you give it a first look and provide feedback pls? 😄
It probably makes sense to define context for global widget options instead of passing them to each component
This is a great idea
It probably makes sense to define context for global widget options instead of passing them to each component
@mpetrunic seeking clarification here: do you mean context for all the widget options that we currently defined as properties or just the ones concerning the wallet connection? Because if this is true for the former, wouldn't make sense to tackle that on a different PR with it's own issue?
It probably makes sense to define context for global widget options instead of passing them to each component
@mpetrunic seeking clarification here: do you mean context for all the widget options that we currently defined as properties or just the ones concerning the wallet connection? Because if this is true for the former, wouldn't make sense to tackle that on a different PR with it's own issue?
I guess, for now just theme options and wallet options^^
btw @mpetrunic I think we might need to expose the ISygmaProtocolWidget
from the react package, because with the react example, there is no type inferring when for instance defining a dynamic theme with setState
btw @mpetrunic I think we might need to expose the
ISygmaProtocolWidget
from the react package, because with the react example, there is no type inferring when for instance defining a dynamic theme with setState
Thats fine
Description
Related Issue Or Context
Closes: #86
How Has This Been Tested? Testing details.
Types of changes
Checklist: