Miha Markič
Miha Markič
After poking a bit I see that this might be tricky to properly implement. The reason is that many arguments aren't compatible with Blazor/WebAssembly. Only atomic types such as numbers...
For the time being I'll add it to milestone 0.7
@pascalberger You are certainly correct. The thing was, that most of the settings were autogenerated from sources, where it isn't evident what string represents. Since then I dropped autogeneration (too...
Good. I will keep in mind this, and if somebody provides PRs, I'll gladly merge them.
Yep, single channel. The thing is that the data comes through from the device, it's just those warnings for some reason. Do you happen to know if there is an...
React is easy, easier that classic stuff. Once you understand it and get some practice, that is. For me a good way to learn it was a course on Pluralsight.
@altishchenko Honestly, I'd like to. Realistically it's really tough time for this for me. There is another approach perhaps, that's more appealing to me these days and I'd try to...
I'm observing the same error - but only when using your sources directly. Works fine from NuGet. I guess there are some project settings.
"Won't putting it in the same place just overwrite the original file?" I imagine using transformed file for compilation somehow. Or perhaps creating transformed file with different name in the...
@natebosch It's the same builder. Separating sources in packages is not an option. Imagine a scenario where I have a type hierarchy and I'd like to add augmentation to all...