npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ember-power-calendar-selectors

v0.1.2

Published

Ember Power Calendar Selectors Addon

Downloads

8

Readme

ember-power-calendar-selectors Build Status

Provides additional date selection components for ember-power-calendar

This project provides alternative date selection components that integrate with ember-power-calendar seamlessly. Currently a months selector (for selecting over years) and a years selector (for selecting over decades) are implemented.

Table of Content

Background

ember-power-calendar-selectors was created to allow for more natural selection of dates in the month, quarter, and year time grains. It only uses the ember-power-calendar public API via the yeilded calendar object.

Install

First install ember-cli-less or ember-cli-sass, ember-power-calendar, and ember-power-calendar-selectors

ember install ember-cli-less ember-power-calendar ember-power-calendar-selectors

Next import the required styles.

for example in app/styles/app.less

@import "ember-power-calendar";
@import "ember-power-calendar-selectors";

.ember-power-calendar {
  .ember-power-calendar(@cell-size: 50px);
  .ember-power-calendar-selectors(@cell-size: 50px);
}

or in app/styles/app.scss

@import "ember-power-calendar";
@import "ember-power-calendar-selectors";

.ember-power-calendar {
  @include ember-power-calendar($cell-size: 50px);
  @include ember-power-calendar-selectors($cell-size: 50px);
}

The above will style all .ember-power-calendars the same, feel free to use custom class names.

Configuration

Beyond Installation, this project does not require other config. Various scss variables can be set on the ember power calendar selectors mixin to change it the selector's look and feel if desired.

Usage

Usage of ember-power-calendar-selectors components is nearly the same as the default ember-power-calendar calendar.days component. The main difference is that the calendar object yielded by power-calendar must be passed into the new ember-power-calendar-selectors selection components.

For example, here is an example of how to render a non-interactive years selector.

<PowerCalendar as |calendar|>
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

For more details see the API.

Security

This project doesn't have any security concerns.

API

Years Selector

The ember-power-calendar-selectors addon provides the power-calendar-months, and power-calendar-years selector components which work similarly to the power-calendar's native calendar.days yielded component. It renders selectors for all the years in a decade.

For example, here is an example of how to render a non-interactive years selector.

<PowerCalendar as |calendar|>
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

When an onSelect handler is provided to power-calendar the power-calendar-years selector becomes interactive and sends events to the handler.

<PowerCalendar 
  @selected={{selected}}
  @onSelect={{action (mut selected) value="date"}}
  as |calendar|
>
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

All the options implemented by calendar.days have been reimplemented by power-calendar-years as well. For example,

<PowerCalendar 
  @selected={{selected}}
  @onSelect={{action (mut selected) value="date"}}
  @minRange={{"2y"}}
  @maxRange={{"5y"}}
  as |calendar|
>
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

works as expected. Be advised, {min,max}Range interpret Number values as days, no matter the subcomponent being rendered. Pass in "{number of years}y" if the range should be specified in years as shown above.

Also, selectors can be used in concert without issue. For instance,

<PowerCalendar 
  @selected={{selected}}
  onSelect={{action (mut selected) value="date"}}
  @minRange={{"2y"}}
  @maxRange={{"5y"}}
  as |calendar|
>
  <calendar.days />
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

will work without a problem.

Finally, selector behavior has been implemented for all the power-calendar selection modes, single, range, and multiple. This,

<PowerCalendarRange
  @selected={{selected}}
  @onSelect={{action (mut selected) value="date"}}
  as |calendar|
>
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendarRange>

will work without further tweaking, as will power-calendar-multiple.

Months Selector

The power-calendar-months component renders with selectors for the 12 months in a year and the quarters by default. It shares most of its API with power-calendar-years with a few notable exceptions.

fisrtQuarter

firstQuarter specifies the starting label of the first quarter. Defaults to 1.

<PowerCalendar
  @selected={{selected}}
  @onSelect={{action (mut selected) value="date"}}
  as |calendar|
>
  <PowerCalendarMonths @firstQuarter={{2}} @calendar={{calendar}} />
</PowerCalendar>

will render with the first quarter of the year as Q2.

showQuarters

Determines if the quarters should be rendered. Defaults true.

<PowerCalendar
  @selected={{selected}}
  @onSelect={{action (mut selected) value="date"}}
  as |calendar|
>
  <PowerCalendarMonths @showQuarters={{false}} @calendar={{calendar}} />
</PowerCalendar>

will not render with quarters, only months.

Selectors Nav

It also provides the power-calendar-selectors-nav component. This component can be used as a more convenient nav for the months, and years selector.

For example, power-calendar-selectors-nav can be used to navigate by decade instead of month, convenient when using the years selector. The dateFormat property can be used to provide custom date format strings. We use moment.js format strings.

<PowerCalendar 
  @onCenterChange={{action (mut center) value="date"}}
  @center={{center}}
  as |calendar|
>
  <PowerCalendarSelectorsNav @dateFormat="Today is the Do of MMMM" @calendar={{calendar}} @by="decade" />
  <PowerCalendarYears @calendar={{calendar}} />
</PowerCalendar>

onSelect Handler

All default behaviors can be handled through the power-calendar onSelect handler hook, just as in base ember power calendar. For instance,

<PowerCalendarRange 
  @onSelect={{action (mut selected)}}
  @selected={{selected}}
  as |cal|
>
  <PowerCalendarMonths @calendar={{cal}} />
</PowerCalendarRange>

Will now properly select the entire quarter range when a quarter is selected by the user.

Most users should have no issue using the default behavior provided by the ember-power-calendar actions. However, the child selector onSelect will directly pass the user the selected dateObj allowing them full control of what is selected if the user requires it. Because of this the child onSelect hook has different behavior that the parent component's on onSelect hook.

In the case that the user desires to discriminate between month and quarter selections, the child onSelect can be leveraged.

<PowerCalendarMultiple @selected={{selected}} as |cal|>
  <PowerCalendarMonths 
    @onSelect={{action "handleSelect"}}
    @calendar={{cal}}
  />
</PowerCalendarMultiple>
{ actions: {
  handleSelect(dateObj) {
    if (dateObj.period === 'quarter') console.log('you clicked a quarter');
    if (dateObj.period === 'month') console.log('you clicked a month');
  }
} }

In the case that both hooks are used all registered handlers fire in order of specificity.

<PowerCalendarRange 
  @onSelect={{action (mut selected)}}
  {{!-- ^fires second --}}
  @selected={{selected}}
  as |cal|
>
  <PowerCalendarMonths 
    @onSelect={{action (mut selected)}}
    {{!-- ^fires first --}}
    @calendar={{cal}}
  />
</PowerCalendarRange>

Contribute

Please refer to the contributing.md file for information about how to get involved. We welcome issues, questions, and pull requests. Pull Requests are welcome.

Maintainers

Alex Aralis: [email protected]

License

This project is licensed under the MIT License.