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

Grouping description endpoint #1310

Open
mathemancer opened this issue Apr 26, 2022 · 2 comments
Open

Grouping description endpoint #1310

mathemancer opened this issue Apr 26, 2022 · 2 comments
Labels
affects: architecture Improvements or additions to architecture needs: implementation specs We need clarity on HOW we'll implement it from a technical perspective type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Milestone

Comments

@mathemancer
Copy link
Contributor

Problem

Currently, we're not exposing hints about how different grouping methods work in the API, so we'd need to hard code some of that information in the front end to make it possible to use grouping to the fullest extent. We shouldn't have to hard code information about how different grouping modes work in the front end.

Proposed solution

We should use hints to give the front end information about how to use different grouping modes. This includes:

  • needed arguments
  • applicable types
  • whether the grouping mode is ranged or not
  • whether the grouping mode is multi-column or not
@mathemancer mathemancer added type: enhancement New feature or request affects: architecture Improvements or additions to architecture work: backend Related to Python, Django, and simple SQL status: draft labels Apr 26, 2022
@mathemancer
Copy link
Contributor Author

@dmos62 I think we can go back-and-forth in this issue about how this should look. Marking as draft until we have more details figured out (e.g., where the endpoint should go).

@github-actions
Copy link

github-actions bot commented Feb 4, 2023

This issue has not been updated in 90 days and is being marked as stale.

@github-actions github-actions bot added the stale label Feb 4, 2023
@seancolsen seancolsen added needs: implementation specs We need clarity on HOW we'll implement it from a technical perspective and removed stale labels Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: architecture Improvements or additions to architecture needs: implementation specs We need clarity on HOW we'll implement it from a technical perspective type: enhancement New feature or request work: backend Related to Python, Django, and simple SQL
Projects
No open projects
Development

No branches or pull requests

3 participants