jfinn/jitsi_corner9 - Gitea: Git with a cup of tea

Grafico dei commit

Autore	SHA1	Messaggio	Data
Lyubo Marinov	2e2129fa44	Import PropTypes from prop-types Prepare for React 16.	7 anni fa
paweldomas	70fc727b92	[RN] Prevent a possible TypeError	7 anni fa
Lyubo Marinov	4dc658c270	Fix 'Missing JSDoc comment require-jsdoc'	8 anni fa
Lyubo Marinov	a9bdde193d	Approach consistent filmstrip naming We seemed to be using the names "film strip" and "filmstrip" (and, consequently, their source code-conscious forms such as film-strip, FilmStrip, etc.) In order to comply with our coding style which requires a consistent one name for a given abstraction, choose one name and rename the uses of the other name. Wikipedia has a definition of a "filmstrip", I couldn't find a "film strip". I guess our abstraction can be seen as what's described there. When I google "film strip", I get results about "filmstrip" at the top. That's why I chose "filmstrip". Certain uses of "film strip" such as interfaceConfig.filmStripOnly and in the external API I left untouched in an attempt to preserve compatibility. I wasn't sure whether CSS was tangled in compatibility so I made a choice and renamed there was well.	8 anni fa
hristoterezov	3ae99ea0b9	feat(overlays): for filmstrip only mode	8 anni fa
hristoterezov	c461e8b63c	ref(overlays): Replace the abstract class for overlays with overlay frame component In this case makes more sense to have overlay frame included in every overlay instead of abstract class that implements the overlay frame and have to be extended by every overlay. In addition, mapStateToProps isn't working well with inheritance.	8 anni fa