Skip to content

New sample: Date Range Picker Component - #202

Open
asdrenbegaj wants to merge 1 commit into
pnp:mainfrom
asdrenbegaj:date-range-picker-component
Open

asdrenbegaj wants to merge 1 commit into
pnp:mainfrom
asdrenbegaj:date-range-picker-component

Conversation

@asdrenbegaj

Copy link
Copy Markdown
  • Bug fix?
  • New sample?
  • Related issues: fixes #X, partially #Y, mentioned in #Z
  • Needs API permissions?
  • Has other prerequisites? (E.g. requires a list, document library, etc.)

What's in this Pull Request?

New sample: Date Range Picker Component, a canvas component (in a component library) for picking a single date or a date range. Booking rules are set through input properties: MinDate, MaxDate, BlockedDates, DisableWeekends, AllowRange, MaxDays and AccentColor. The app reads StartDate, EndDate, DayCount and IsComplete from output properties.

It's an input control, so it complements the existing Calendar Component sample (which displays events) rather than duplicating it.

No data sources, no premium features, no experimental features. A live demo of the logic is linked from the README.

Tested: imported the solution, added the component with Get more components, and tested single-day and range selection, blocked dates, MaxDays, weekends off, two instances on one screen and Reset.

Checklist

  • My pull request affects only ONE sample.
  • My sample includes a completed assets/sample.json metadata file.
  • I have updated the sample's README.md.
  • My README has at least one static high-resolution screenshot (i.e. not a GIF).
  • My README contains complete setup instructions, including prerequisites and required permissions.
  • The final line of my README is <img src="https://m365-visitor-stats.azurewebsites.net/powerplatform-samples/samples/date-range-picker-component" />.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant