Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@fluentui/react-datepicker-compat

Package Overview
Dependencies
Maintainers
12
Versions
526
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@fluentui/react-datepicker-compat

React components for building web experiences

  • 0.4.57
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8.4K
decreased by-22.21%
Maintainers
12
Weekly downloads
 
Created
Source

@fluentui/react-datepicker-compat

React Datepicker components for Fluent UI React

Picking a date can be tough without context. A date picker (DatePicker) offers a popup control that’s optimized for picking a single date from a calendar view where contextual information like the day of the week or fullness of the calendar is important. You can modify the calendar to provide additional context or to limit available dates.

Usage

To import DatePicker:

import { DatePicker } from '@fluentui/react-datepicker-compat';

Examples

<DatePicker />

Alternatively, run Storybook locally with:

yarn workspace @fluentui/react-datepicker-compat start

Compat component

What makes a compat component?

A compat component is a component taken from v8 and partially updated with the v9 toolset while keeping its original functionality and most of the original API surface. The most noticeable change being the removal of all v8 dependencies and using only v9 dependencies. While this is a good first step, this is not the final v9 component. We are working on a fully fleshed v9 replacement that will follow all v9 patterns and conventions.

How publishing the package will be handled

Compat components are not added in the @fluentui/react-components package suite. Instead, these components should be imported from their respective package as shown above. In contrast with components that live in @fluentui/react-components, compat components are to be released as 0.x.x and there won't be an unstable release (beta/alpha) before this release. This is due to the way we will handle versioning for changes, allowing for breaking changes when necessary.

Versioning for changes

We will take a similar approach as v0 where we will follow this pattern:

  • breaking change (major): Since this is a compat component, we will allow breaking changes if absolutely necessary. To accommodate for this, we will denote those changes as a minor version in semver, i.e. 0.(change will be reflected here).x.
  • minor and patch: These changes will be reflected in the patch version in semver as 0.x.(change will be reflected here).

FAQs

Package last updated on 09 Dec 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc