-
In a similar vein to #203, a unified ordering solution seems like a necessity. Ordering with STAPI seems to be confined to supporting tasking orders, understandingly, but ordering from archive is also…
-
**Description:**
During move ordering, moves are currently given a "base score" that is modified through move ordering techniques such as MVV-LVA and (once #67 merges) History Heuristic.
Instead of …
-
## User Interface for Ordering Provider Management
### Why should we do this?
- Currently, SimpleReport users are unable to manage multiple ordering providers associated with their facility. This …
-
In Appendix A.1 step 4, the user should be prompted for their activation secret before the client can sign the challenge, since the activation secret unlocks the signing key. In the draft, these oper…
-
As discussed in issue #169, to improve modularity it makes sense to replace the explicit construction sequence by a set of construction pattern dependencies, leaving csv2nq to compute a partial orderi…
-
### Summary
When multiple inlay hints share the same position they are ordered inconsistently. The order might change after a seemingly unrelated change. Note that LSP prescribes a set order:
> If…
-
**Is your feature request related to a problem? Please describe.**
LazyGit currently orders items in the `Files` pane in a directory-first, uppercase-first ordering. My other applications (`ls`, V…
-
The current stroke dash description is a bit sparse and doesn't cover element ordering and what is and isn't valid. For example, is it valid to have multiple dash elements in a row?
I know Skottie …
-
Create a new order using tasks.
Design and notes here: https://www.figma.com/design/wVmz098ZrSxswOI0nbIjQ2/Design-system-Tolgee?node-id=1713-29712
-
### Describe the bug
Saving lazy dataframe with `polars save` results in loss of order.
### How to reproduce
1. run `1..10 | each { |i| {i: $i}} | polars into-lazy | polars save test.csv` or with s…