feat: improve project structure about fast-blazor HOT 6 CLOSED

I can definitely see re-organizing the components. I think I'd like to keep the enum and associated extensions together if possible. Can you share a bit about what the use cases are for css and js in this project? I can't see us adding css, as that is contained in the core web components themselves. What about JS? Is that for interop scenarios?

from fast-blazor.

Definitely CSS it's not going to be needed, but JS interop is probably going to be since some of the components logic just work better if you call them using JS Interop, also we wouldn't have to reinvent the wheel for the logic if we just use JS.

I'm going to make a pull request so the changes can be seen.

from fast-blazor.

@emimontesdeoca That sounds good. Maybe make a small PR to just change one or two components so we can take a look. There are a couple of other component PR updates in progress, which we may need to get merged first. So, it might be better to use your PR purely as an example with the idea that we may need to do a separate PR later for the actual change.

from fast-blazor.

@EisenbergEffect I've been busy these weeks, I'll try to have the PR done by this weekend 😊!

from fast-blazor.

Sounds great. We understand the business ;) We've had a lot going on as well. Thanks for working with us!

from fast-blazor.

I'm going to close this for now. We certainly welcome improvements to the project structure in the future whenever time/interest permits.

from fast-blazor.