microsoft / microsoft/aspire

Interactive InputType and range limiting

Open
#15,646 0 comments 1 reaction 0 assignees View on GitHub
area-app-model interaction-service
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

We require InteractiveInput to support both numeric and date time values with/without range limitation; at present we are using the InputType.Choice generating all possible values as text dynamically.

We would like first class support for range limitation and DateOnly, TimeOnly, DateTime input type.

### Describe the solution you'd like

We'd like to be able to support date time, date, time values as part of the InteractiveInput with the use of a DatePicker with range limiting that would also apply to the InputType.Number

InputType = [ InputType.Number || **InputType.Date** || **InputType.Time** || **InputType.DateTime** ],

**MinValue = lowerLimitOfInputType**
**MaxValue = upperLimitOfInputType**

MinValue, MaxValue would be optional

### Additional context

InteractiveInput has limited types, these are proving somewhat restrictive and require additional repetative code to provide the needed functionality and support for **DateTime**, **DateOnly**, **TimeOnly** value types and value **range** limiting.

It would be good if these types be extended to include the above; with the addtion InteractiveInput properties to support range limiting of Value; MinValue, MaxValue.

At present we are using the InputType.Choice generating all possible values as text within the **DynamicLoading**.
We would like first class support for _range limitation_ and new InputType **DateOnly**, **TimeOnly**, **DateTime** input type.

Contributor guide

Open the contributing guide

Research direction

Start by locating the InteractiveInput and InputType definitions and the existing DynamicLoading usage described in the issue. Review how current choice and numeric inputs are represented, then define the scope for date, time, DateTime, DateOnly and TimeOnly values plus optional bounds; done means the supported input types and range behavior are specified and covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.