Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@kalamazoo/textfield

stevenselcuk9Apache-2.01.0.2TypeScript support: included

Text Field Component

atlaskit, react, ui

readme

Textfield

Provides a standard way to create a text-based form input.

Installation

yarn add @kalamazoo/textfield

Usage

Detailed docs and example usage can be found here.

changelog

@kalamazoo/textfield

3.1.4

Patch Changes

3.1.3

Patch Changes

  • [patch]557a8e2451:

    Rebuilds package to fix typescript typing error.

3.1.2

Patch Changes

  • [patch]35d2229b2a:

    Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.

3.1.1

Patch Changes

  • [patch]a2d0043716:

    Updated version of analytics-next to fix potential incompatibilities with TS 3.6

3.1.0

Minor Changes

  • [minor]9638c553c0:

    Adding an optional prop testId that will set the attribute value data-testid. It will help products to write better integration and end to end tests.

3.0.7

Patch Changes

  • [patch]d5def52d98:

    Refactored textfield styles to better support border-box being set globally.

3.0.6

3.0.5

Patch Changes

  • [patch]097b696613:

    Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports

3.0.4

Patch Changes

3.0.3

Patch Changes

  • [patch]708028db86:

    Change all the imports to theme in Core to use multi entry points

3.0.2

Patch Changes

  • [patch]de35ce8c67:

    Updates component maintainers

3.0.1

3.0.0

Major Changes

  • [major]84887b940c:

    • Converting from flow to typescript 🎉
    • Correctly typing the current prop spreading onto the internal <input> element
    • Removing isHovered and isFocused from public API as they previously did not do anything

2.0.5

Patch Changes

  • [patch]2fe6e8fbdf:

    Removed unused dependencies from package.json for textfield: @emotion/core was unused.

2.0.4

Patch Changes

  • [patch]9f8ab1084b:

    Consume analytics-next ts type definitions as an ambient declaration.

2.0.3

2.0.2

Patch Changes

  • [patch]4615439434:

    index.ts will now be ignored when publishing to npm

2.0.1

2.0.0

  • [major]7c17b35107:

    • Updates react and react-dom peer dependencies to react@^16.8.0 and react-dom@^16.8.0. To use this package, please ensure you use at least this version of react and react-dom.

1.0.0

  • [major]6cdf11238d:

    • This major release indicates that this package is no longer under dev preview but is ready for use

0.4.5

  • [patch]7157a95389:

    • Internal changes only. Textfield is compatible with SSR.

0.4.4

0.4.3

0.4.2

  • [patch]a28eb04426:

    • Migrates package from emotion 9 to emotion 10. No behaviour or API changes.

0.4.1

  • [patch]e0797c2937:

    • Support object refs e.g. React.createRef()

0.4.0

  • [minor]8eff47cacb:

    • Allow element before and/or after input

0.3.1

0.3.0

  • [minor]76299208e6:

    • Drop ES5 from all the flow modules

    Dropping CJS support in all @atlaskit packages

    As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only distribute esm. This means all distributed code will be transpiled, but will still contain import and export declarations.

    The major reason for doing this is to allow us to support multiple entry points in packages, e.g:

    import colors from `@kalamazoo/theme/colors`;

    Previously this was sort of possible for consumers by doing something like:

    import colors from `@kalamazoo/theme/dist/esm/colors`;

    This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.

    To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.

    ES Modules are widely supported by all modern bundlers and can be worked around in node environments.

    We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.

    Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support (for external) if you have any questions or queries about this.

0.2.0

  • [minor]e9b824bf86:

    • Breaking: Changes to the theme prop. The type of this prop remains as (ThemeTokens, ThemeProps) => ThemeTokens.
      • The shape of ThemeTokens has changed. container and input keys are now required. The value of these keys are style objects.
      • More information has been added to ThemeProps.
    type ThemeTokens = {
- backgroundColor: string
- backgroundColorFocus: string
- backgroundColorHover: string
- borderColor: string
- borderColorFocus: string
- textColor: string
- disabledTextColor: string
- placeholderTextColor: string
+ container: Object,
+ input: Object
}

type ThemeProps = {
  appearance: ThemeAppearance,
  mode: 'dark' | 'light',
+  isDisabled: boolean,
+  isFocused: boolean,
+  isHovered: boolean,
+  isInvalid: boolean,
+  isMonospaced: boolean,
+  isCompact: boolean,
+  width?: string | number,
};

0.1.6

  • [patch]3d8322bd71:

    • Trival refactor: update a variable name

0.1.5

0.1.4

0.1.3

  • [patch]63f969d:

    • Fixed height of compact textfields to correctly be 32px instead of 28px

0.1.2

  • [patch]480a57c:

    • Convert to use new theme API.

0.1.1

0.1.0

  • [minor]62109bd:

    • Refactor of field-text to remove field-base and normalise along api patterns established in other form components.