mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-15 09:22:43 +03:00
00e86292ac
`IndexMap::remove` has been deprecated in favor of `IndexMap::swap_remove` (which has the same behavior, but is clearer about breaking ordering) or `IndexMap::shift_remove`, which retains order but is O(n) complexity. I have taken a look at the areas where we use `.remove`. Where we discard the map afterwards, I've changed it to `.swap_remove`. In one case, we do return the data in the event of error, but we probably care more about consistency of ordering than the actual precise order, so I've used a `HashMap` and just sorted it instead. V3_GIT_ORIGIN_REV_ID: 479e1013a4a9938f973b5ed85dbf3837896151e4 |
||
|---|---|---|
| .. | ||
| custom-connector | ||
| engine | ||
| hasura-authn-core | ||
| hasura-authn-jwt | ||
| hasura-authn-webhook | ||
| lang-graphql | ||
| open-dds | ||
| opendds-derive | ||
| recursion_limit_macro | ||
| tracing-util | ||