-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Conversation
Build is broken b/c Popover2 depends on Tooltip2
923f2d7
to
e7032c8
Compare
Ignore test coverage for these files for nowPreview: documentation |
Merge branch 'master' into cl/graduate-labs-to-corePreview: documentation |
@@ -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: |
There was a problem hiding this comment.
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", |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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"; |
There was a problem hiding this comment.
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?
Move
TagInput
,Popover2
, andTooltip2
fromlabs/
intocore/
.Next steps (each in a separate PR, probably):
Tooltip
andPopover
fromcore/
; renamePopover2
andTooltip2
toPopover
andTooltip
, respectively; deletetether
dependency; fix build failures.Popover2.isDisabled
).Tooltip2
,Popover
, andTagInput;
and remove them from karmacoverageExcludes
.