Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standalone calendar #9203

Open
mjuniper opened this issue Apr 26, 2024 · 2 comments
Open

Standalone calendar #9203

mjuniper opened this issue Apr 26, 2024 · 2 comments
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Hub Issues logged by ArcGIS Hub team members. design Issues that need design consultation prior to development. estimate - design - lg Large design effort; 10-20 days of design work impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone new component Issues tied to a new component. p - low Issue is non core or affecting less that 10% of people using the library

Comments

@mjuniper
Copy link
Member

Description

We would like to have a standalone calendar component into which we could render events on specific days. Something like this:

image

User Stories

As a developer I want to render events on an interactive calendar.

Acceptance Criteria

It should look similar to the calcite-date-picker and allow rendering events on specific days.

Relevant Info

No response

Helpful Details

I'm not sure if this is the best approach but an api that comes to mind is to use dynamic slots for inserting events into specific days, something like this:

<calcite-calendar {...props-similar-to-date-picker}>
  <calcite-calendar-event slot="2024-05-17">an event</calcite-calendar-event>
  <calcite-calendar-event slot="2024-05-17">another event</calcite-calendar-event>
  <calcite-calendar-event slot="2024-05-25">another event on a different day</calcite-calendar-event>
</calcite-calendar>

I did an extremely rough prototype of that approach and it works but I don't know if there are perf or other implications.

Priority impact

p3 - want for upcoming milestone

Esri team

ArcGIS Hub

@mjuniper mjuniper added 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. new component Issues tied to a new component. labels Apr 26, 2024
@github-actions github-actions bot added ArcGIS Hub Issues logged by ArcGIS Hub team members. p3 - want for upcoming milestone labels Apr 26, 2024
@geospatialem geospatialem added the design Issues that need design consultation prior to development. label Apr 26, 2024
@geospatialem geospatialem added p - low Issue is non core or affecting less that 10% of people using the library estimate - design - lg Large design effort; 10-20 days of design work labels May 9, 2024
@geospatialem geospatialem added this to the Design Backlog milestone May 9, 2024
@geospatialem geospatialem removed the needs triage Planning workflow - pending design/dev review. label May 9, 2024
@geospatialem geospatialem added impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone and removed p3 - want for upcoming milestone labels May 21, 2024
@brittneytewks brittneytewks self-assigned this Aug 30, 2024
@brittneytewks
Copy link

brittneytewks commented Aug 30, 2024

@mjuniper synced up with @ajturner yesterday on this request. Right now, we don't have capacity to prioritize full designs and implementation of this component but he'll be working with the team to summarize Hubs version of use cases + requirement + patterns and we'll continue to connect on needs and what future implementation could look like.
cc: @macandcheese, @SkyeSeitz, @geospatialem

@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Aug 30, 2024
@geospatialem geospatialem added the spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. label Dec 20, 2024
@geospatialem geospatialem removed this from the Design Backlog milestone Dec 20, 2024
@geospatialem
Copy link
Member

Set as a spike to kickstart the effort with @samanthahunter and the Hub team in early 2025. ✨🤜🏻🤛🏻✨

@SkyeSeitz SkyeSeitz removed the spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Hub Issues logged by ArcGIS Hub team members. design Issues that need design consultation prior to development. estimate - design - lg Large design effort; 10-20 days of design work impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone new component Issues tied to a new component. p - low Issue is non core or affecting less that 10% of people using the library
Projects
None yet
Development

No branches or pull requests

5 participants