Skip to content

Conversation

@AdityaHegde
Copy link
Collaborator

@AdityaHegde AdityaHegde commented Oct 29, 2024

Backend checklist

  • Add module for parsing rill time syntax in backend.
  • Add ResolveTime to return start and end times based on minTime, maxTime and now for a metrics view.
  • Replace usage of old duration parser.
  • Map old format to new format
  • Add API to resolve times for a list of rill-times.
  • Add a lot more tests.

UI checklist

  • Add a parser in UI.
  • Check if we really need to replicate the parser in UI. We could make the resolve time API to return parsed object as well.
  • Integrate the new API to get start and end in UI.
  • Categorise the time ranges into latest periodToDate and previous
  • Add conversion to human readable label.
  • Add E2E tests around time.
  • Docs for the new rill time syntax @medriscoll

@AdityaHegde AdityaHegde force-pushed the feat/rill-time-range-syntax branch from 88614f4 to 396044d Compare November 14, 2024 09:21
@AdityaHegde AdityaHegde force-pushed the feat/rill-time-range-syntax branch from e6be55f to bbbe3d5 Compare November 20, 2024 16:02
@AdityaHegde
Copy link
Collaborator Author

Closing this since frontend code is pretty stale with human readable url changes. Will open separate PRs for backend and frontend.

@AdityaHegde AdityaHegde deleted the feat/rill-time-range-syntax branch December 23, 2024 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants