Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Question: why FluentInputBase.cs and not Blazor's InputBase.cs?
See original GitHub issueJust found out about the existence of this package today. I think it’s pretty cool as it makes it simpler to adopt the FAST Fluent components in a Blazor project 😃.
Navigating through the code it came to my attention the fact that all input-like components (for ex. FluentTextField) derive from a FluentInputBase.cs (link), which is almost an exact, line-by-line duplicate of Blazor’s InputBase.cs (link) base class for input elements. I was wondering what was the reason for this divergence? Is the plan to eventually make all input components in this package derive from the latter?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
With .NET 6 the requirement for an EditContext is no longer there (https://github.com/dotnet/aspnetcore/commit/afacc8740c40bf465da9b9a34914a2d88d243b3c). We should change to derive from InputBase
Closing this since I think we answered the question. We can revisit code changes at a later point based on future Blazor releases.