Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graduate Labs Components - Part 1: Move TagInput, Popover2, Tooltip2 into core/ #1881

Merged
merged 21 commits into from
Dec 12, 2017

Conversation

cmslewis
Copy link
Contributor

@cmslewis cmslewis commented Dec 11, 2017

Move TagInput, Popover2, and Tooltip2 from labs/ into core/.

  • Ignore test coverage on these files for now; will write tests and unignore as a follow-up.

Next steps (each in a separate PR, probably):

  1. Delete Tooltip and Popover from core/; rename Popover2 and Tooltip2 to Popover and Tooltip, respectively; delete tether dependency; fix build failures.
  2. Migrate deprecated internal usages to new props (e.g. Popover2.isDisabled).
  3. Write tests for Tooltip2, Popover, and TagInput; and remove them from karma coverageExcludes.

@blueprint-bot
Copy link

Ignore test coverage for these files for now

Preview: documentation

@blueprint-bot
Copy link

Merge branch 'master' into cl/graduate-labs-to-core

Preview: documentation

@cmslewis cmslewis changed the title Move TagInput, Popover2, Tooltip2 from labs/ into core/ Graduate Labs Components - Part 1: Move TagInput, Popover2, Tooltip2 into core/ Dec 12, 2017
@adidahiya adidahiya requested review from gscshoyru and removed request for adidahiya and jkillian December 12, 2017 00:41
@@ -11,6 +11,10 @@ module.exports = function (config) {
dirname: __dirname,
coverageExcludes: [
"src/accessibility/*",
// TODO (clewis): write tests for these component as part of the 2.0 effort:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about Popover2Tests?

"pure-render-decorator": "^1.1",
"react-popper": "~0.7.4",
"tether": "^1.4",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kill it with 🔥 🔥 🔥


`TagInput` renders [`Tag`](#core/components/tag)s inside an input, followed by an actual text input. The container is merely styled to look like a Blueprint input; the actual editable element appears after the last tag. Clicking anywhere on the container will focus the text input for seamless interaction.
Tag inputs render [`Tag`](#core/components/tag)s inside an input, followed by an actual text input. The container is merely styled to look like a Blueprint input; the actual editable element appears after the last tag. Clicking anywhere on the container will focus the text input for seamless interaction.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm I preferred the TagInput usage to clarify that it's one thing (not two words) and that there's only a React API for it.

import * as Classes from "../../common/classes";
import * as Keys from "../../common/keys";
import { HTMLInputProps, IProps } from "../../common/props";
import * as Utils from "../../common/utils";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could import just the used utils?

@cmslewis cmslewis merged commit c344fae into master Dec 12, 2017
@cmslewis cmslewis deleted the cl/graduate-labs-to-core branch December 12, 2017 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants