[Cleanup] Avoid storing preferences maxTimeMS in compass-aggregations state

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 1.42.3
    • Affects Version/s: None
    • Component/s: Aggregation pipeline
    • None
    • 2
    • Iteration Utahraptor, Iteration Velociraptor, Iteration Wendiceratops, Iteration Xiaosaurus
    • Not Needed
    • Developer Tools

      We shouldn’t need to separately keep track of the preferences maxTimeMS value in the redux slice in compass-aggregations. Instead, we should use React usePreference() for frontend components and the redux thunk argument for actions.

            Assignee:
            Basit Chonka
            Reporter:
            Anna Henningsen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: