Droplist
This is a base (internal) component which should be used to build all the 'dropdown' lists.
Installation
yarn add @kalamazoo/droplist
Usage
Detailed docs and example usage can be found here.
Droplist component
This is a base (internal) component which should be used to build all the 'dropdown' lists.
yarn add @kalamazoo/droplist
Detailed docs and example usage can be found here.
[minor]0e2241e904:
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.
[patch]35d2229b2a:
Adding missing license to packages and update to Copyright 2019 Atlassian Pty Ltd.
[patch]a2d0043716:
Updated version of analytics-next to fix potential incompatibilities with TS 3.6
[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
[patch]ecca4d1dbb:
Upgraded Typescript to 3.3.x
[patch]708028db86:
Change all the imports to theme in Core to use multi entry points
[patch]de35ce8c67:
Updates component maintainers
[patch]d905cbc0ac:
Adding a condition to check if the component are referenced in tests running in CI. It reduces the noise and help reading the CI log.
[patch]226a5fece8:
Upating deprecation messages and adding console warning to improve visibility
[patch]27ae405d29:
Removed unused dependencies from package.json for droplist: keycode and classnames were unused.
[patch]9f8ab1084b:
Consume analytics-next ts type definitions as an ambient declaration.
[patch]6fe990954c:
Adjusted the offset prop for Popper to not use the deprecated format
[patch]4615439434:
index.ts will now be ignored when publishing to npm
[patch]b0ef06c685:
[patch]21854842b5:
[major]7c17b35107:
[patch]6fd20256f3:
[patch]98e11001ff:
[major]76299208e6:
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.
[patch]08d8be9370:
[patch]7fbe95e:
isMenuFixed
prop to force menu to render with position fixed to allow it to break out of non-visible overflow containers at the cost of scroll detachment. e20ac40shouldAllowMultilineItems
(6af80cc)