Satyajit Sahoo

> Maybe it would be simpler if we allow developers to apply anything they wish on the One concern would be that it might be easy to break the editor...

> not wanting to make a PR each time I need to extend something I think so far there haven't been many cases like this.. If we want to remove...

> @sassanh `` React is a cross-platform framework (React Native, Ink, other custom renderers etc.), so DOM-specific props on `React.Fragment` is unlikely.

Hi. The project is no longer maintained, since it won't be able to support newer versions of GTK themes written in Sass.

@farwayer Sorry. I think it'll better to have a seprate file and add a include file line in the main gtkrc.

What you have to add is, ``` * { background-color: inherit; color: inherit; } ``` But that's a hack, and causes issues in vanilla Gnome. Anyways, the universal selector is...

> Most concerns I have regard [this useEffect](https://github.com/callstack/react-native-paper/pull/3777/files#diff-df7f1205b408a8b779895c080c77457728df4da79a0fa852c0255e54ce897664R83) where I'd assign dir to the root element of a page (). This handles most cases since the react-native-web looks all the...

Let's move the index file to common directory and change each type (legacy, new, mixed) to have this format for the view and module.

@martintreurnicht that seems like a bug. can you open a bug report about it?

@Grohden can you send a PR?