Safari

IE 11

Still discussing whether this should be a new LabeledRadioButton composite component that leverages RadioButton or some other approach (I think we're all in agreement that we don't want to add label as a prop to RadioButton).

Build a banner component

Related to jira ticket ANXR-194

• create component
• add tests

• refactor out validation by creating another ValidatedTextField component
• add reducers
• add stateful example
• ensure props can take over state when using the stateful version
• add onSubmit callback with standard (value, { event, props }) => {} signature

As part of our common tests, we should make sure the component hangs off our index file. This should help reduce the number of times we forgot to add a component to the index file.

For some reason the composes feature of docgen isn't working with ContextMenu.

• Confirm that all variable are name correct.
• Change less fade to tint and fix any hacks that are related to it
• Move any reusable style in to mixins

Related to ANXR-193.

There is a bug with getAllAsProps in the child-components file. We should also change some of the names of those functions to be more clear.

The problem is because I included normalize in the docs page. Looks like our styling for the RadioButton was implicitly relying on some browser styles.

• add sidebar for navigation
• add code collapsing
• differentiate "composite" components. I believe docgen already has Component.composes which suits our need.
• support markdown in the description and put in on the page
• support markdown in props descriptions
• sort props alphabetically
• show default prop values
• add support for ordering examples
• fix nav scroll overflow

A toggle meant to be used as a replacement for a native radio button element.

Related Jira issue: ANXR-280

We don't need to show all the props for individual icons, they don't really make sense at that level.

Also, the icons need to be normalized to fit a 16px square box so we don't need to handle one off padding per icon.

There is a warning on the console that stroke-width should be strokeWidth

As per David Maloney:

Here's what needs to happen to it so it matches the checkboxes:

Container: Needs to increase in size to 16px x 16px
Dot: Needs to bump up it's left and top positions to 4px
Glow: Needs to bump up it's left and top positions to 4px

Update the color palette to match designs

This would match it with the behavior of a regular TextField

we need an set of SVG icons.

Here is the relevant section of code that would need to be modified. We'll want to use Link from react-router with something like this:

<Link to={`/components/${componentName}`}>...</Link>

some components have requried props or children and generic-tests needs a way to pass those in. also generic-tests uses displayName all over the place but never tests that it exists in the first place, so it's confusing when an unrelated test breaks.

Add a Portal component.

adding normalize to our stack

I think this was caused by #49

Create a new component Tabs.

#86... but with a check box. :)

Found an issue with Tabs when I pulled lucid into another app.

tests should be added for existing util modules

Related to ANXR-279

when passing child components as a props array, all element must be the same shape or a warning message is logged, it should support differently shaped, valid elements in the same child component props array.

describeWithDOM would lazily load and initialize jsdom when a test needed it, however it needs to be initialized before the React global is initialized or else React throws errors on render.

The stateful Tabs aren't working. I have a hunch this might be related to #87.

Label associated with a form control (similar concept to the native HTML label element).

Ref ANXR-312.

#86... but with a switch. :)

A toggle that uses the on/off switch visualization made popular by smartphone OSes to reflect its current state. This is meant to be used as a replacement for a native check box element.

Related Jira issue: ANXR-216

Related to ANXR-192.

Occasionally we'll get an error about value being undefined. This is typically caused by an issue with docs parsing. Let's add better error messages around it.

Current signature on Tabs onSelect:

(index, props) => {}

Proposed signature:

(index, { event, props }) => {}

GitHub has a new PR template feature. We should add one that reminds people to test cross browsers, unit test, etc.

Tweaks in how they're built up following how I decided to do them for the in progress RadioButton component.