Chris Pearce chris-pearce

I hereby claim:

To claim this, I am signing this object:

App Conventions

Components should be written as function components only. In case they need access to local state and/or side-effects (life cycle methods) Hooks should be used. That is, no ES6 classes anymore.
Follow the Container and Presentational design pattern.
Only use index.js files for exporting modules and don't use them within every folder instead reserve them for root folders such as src/components.
All component props should have type definitions using the prop-types library.
For components, use an arrow function.
Destructure props consistently, i.e., pick a way and stick to it.

I hereby claim:

To claim this, I am signing this object:

	document.addEventListener('focusin', () => {
	if (!modal.contains(document.activeElement) {
	firstModalFocusable.focus();
	}
	});

	<button class="header-nav-button time-icons time-icons-menu" type="button"
	aria-label="Navigation menu">
	<span class="h-hide-visually">Navigation menu</span>
	</button>

	<button type="button" class="gb_b" aria-haspopup="true" tabindex="0" aria-expanded="false"
	aria-label="0 Google notifications" title="0 Google notifications">
	<div class="gb_qc gb_rc gb_Rb"></div>
	</button>

	<nav role="navigation" aria-label="Site">
	<ul>
	<li><a href="/">Home</a></li>
	<li><a href="/about">About</a></li>
	<li><a href="/blog">Blog</a></li>
	<li><a href="/contact">Contact</a></li>
	</ul>
	</nav>

	// https://flow.org/en/docs/react/types/#toc-react-elementprops
	React.ElementProps<typeof PostUpgradePrompt>

	<span aria-hidden="true">—</span>
	<span class="h-hide-visually">None so far</span>