ni / ni/nimble

nimble-date-time-text Component

Open
#294 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement new component
Dominant language
TypeScript
Stars
39
Forks
14
Avg merge
1d 16h
Merged PRs (30d)
13

Description

😯 Problem to Solve

Need to create a new Nimble component to display dates and times with consistent formatting (component name is open for debate). This was requested by the Transportation BU (screenshot below; contact Jonathan Meyer or Deborah Bryant for more info) but could be useful in other places.

💁 Proposed Solution

GitHub built some elements that we may be able to leverage: https://github.com/github/time-elements

  • Visual Design: not requested yet

image

Requirements/features
  • duration (3 minutes), absolute time (3:00, November 2nd, 2021)
  • display formatting including people-friendly options ("yesterday" or "5 minutes ago" or "just now")
  • localization and regional formatting (12 vs 24 hour, YMD order, etc)

📋 Tasks

  • nimble-date-time-text interaction design issue
  • nimble-date-time-text interaction design spec
  • nimble-date-time-text visual design issue
  • nimble-date-time-text visual design spec
  • nimble-date-time-text spec
  • nimble-date-time-text custom element
  • nimble-date-time-text unit tests
  • nimble-date-time-text Storybook tests
  • nimble-date-time-text Storybook docs
  • nimble-date-time-text Angular wrapper
  • nimble-date-time-text Blazor wrapper
  • Add to Angular example app
  • Add to Blazor example app
  • Update Component Status table in README and incubating status

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the requirements and the linked GitHub time-elements project, then resolve the open component name and the interaction and visual design work. No implementation file or failing test is named; the issue is done only after the design, custom element, tests, Storybook work, framework wrappers, example apps, and README status updates are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.