Stuck on an issue?

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.

Resolving styling and using ready components (i.e Material UI)

See original GitHub issue

Problem

Styling is so difficult here especially when trying to work with design system components such as Material UI #437 .

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

ksorvcommented, Jul 27, 2020

@ro-ka It’s not about Material UI, i think.

It’s more about providing control to the Developer who wants to the components.

We should atleast provide devs with demos on how to achieve that.

1reaction

belhassen07commented, Nov 23, 2019

Or please add renderInput like renderSuggestItem

Top Results From Across the Web

How to customize - Material UI - MUI

Learn how to customize Material UI components by taking advantage of different strategies for specific use cases.

Migrating to v5: getting started - Material UI - MUI

Material UI v5 includes many bug fixes and improvements over v4. Chief among these improvements is the new styling engine, which offers significant...

Introducing MUI Core v5.0

While the styled() API is great to style complex components or to create highly reused components, there are cases where it's overkill. We ......

@mui/styled-engine - Material UI

The default style library used for generating CSS styles for MUI components is emotion. All of the MUI components rely on the styled()...

Composition - Material UI - MUI

To provide maximum flexibility and performance, MUI needs a way to know the nature of the child elements a component receives. To solve...