-
Notifications
You must be signed in to change notification settings - Fork 0
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
26 global variables #39
Conversation
/// <summary> | ||
/// Set a global variable that is passed to every component on render. | ||
/// </summary> | ||
public Task SetGlobalVariable(string key, object value) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps its a better idea to use properties for these instead of methods? Seems unecessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine for me. We should think about how to handle multiple registrations of the same global variable name though. A simple warning might be sufficient.
…t/set methods for global variables.
No description provided.