I don't see how dropping this component (and also solid support for it) and/or moving it to another host solves anything for the people who use it Just for the lab, I would start with the Slider. As for me, I see so many areas that have a higher ROI, that I don't want to invest time in this component. So far, I think that its who has invested the more time in this component. If I had to guess, I would say that we have only put 30% of what this component will require us in terms of time. Now, to get to this stable state, it requires a lot of effort (time) from the maintainers, people like you who help and people like who report bugs. They won't have to fight with crazy bugs, have to rewrite their code every month, etc. Our users have the guarantee it will provide them a net ROI. We guarantee the quality of the components we host in the core. Implementing the speed dial functionality within the new floating action button component means that this component can be deprecated (and eventually removed), and it follows the guidelines of the floating action button as Moving a component to the core or to a stable state has a strong implication. If you choose to drop it, or not find a solution for a replacement within this package, then you are not keeping to this statement you made.Īs I see it, the new floating action button can perfectly fit the use case of the speed dial: I don't see how dropping this component (and also solid support for it) and/or moving it to another host solves anything for the people who use it, because this is something that is defined in the spec, and I am quoting this directly from the website: "Once we implement the Material design specification (which is a bar set quite high), you should be able to take advantage of it for you own business with any style customization needed." This already explains the major difference between views, and are not related due to a low interest.įurthermore, you can also see if someone in the community is willing to work on getting it ready to be moved to the core (which offered, and which I am willing to do as well in my free time next week), rather than dropping it or having it moved to another host package. I believe that it is better to mark the current component as deprecated, and start working on a new one, rather than just dropping it the view count between components in the core and components in the lab are in my eyes not comparable, because of course the majority of people will look under "Component Demos" or "Component API" rather than some ambiguous label named "Lab", which under the about section states that it "hosts the incubator components that are not yet ready to move to the core", making it seem like they are unstable and are subject to (breaking) change. If I search for react speed dial in a search engine, the first link is a package built on top of the old FAB component ( link), and the second link is to this component. I can imagine that I am not the only one who uses this component because it makes the most sense in certain layout contexts.Īnd let's say that you do make the decision to drop it, how would you suggest that we reimplement this functionality ourselves? Do you plan on writing up a migration document so we keep the same functionality with ease? Or do you plan on disappointing a part of your user base? The functionality of it is fine as is, although it does need a good refactoring.Īt work, we use this component in quite a few places in our application, because any other button component makes no sense and requires a vigorous rework of the layout (something which we will not do for the foreseeable future, as our current layout is fine). Just because the adoption is low, doesn't mean that you should drop it. Maybe the adoption of this component could be low due to the fact that it's still marked as a lab component?
0 Comments
Leave a Reply. |