Skip to content

Commit

Permalink
Automated PR for router-bridge release: router-bridge@v0.5.13+v2.6.2 (#…
Browse files Browse the repository at this point in the history
…435)

mark fields as pub
  • Loading branch information
Geal authored Dec 12, 2023
1 parent c3a3107 commit 4c89f5c
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion federation-2/Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion federation-2/router-bridge/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "router-bridge"
version = "0.5.12+v2.6.2"
version = "0.5.13+v2.6.2"
authors = ["Apollo <packages@apollographql.com>"]
edition = "2018"
description = "JavaScript bridge for the Apollo Router"
Expand Down
6 changes: 3 additions & 3 deletions federation-2/router-bridge/src/planner.rs
Original file line number Diff line number Diff line change
Expand Up @@ -705,7 +705,7 @@ pub struct IncrementalDeliverySupport {
pub struct QueryPlannerDebugConfig {
/// If used and the supergraph is built from a single subgraph, then user queries do not go through the
/// normal query planning and instead a fetch to the one subgraph is built directly from the input query.
bypass_planner_for_single_subgraph: Option<bool>,
pub bypass_planner_for_single_subgraph: Option<bool>,

/// Query planning is an exploratory process. Depending on the specificities and feature used by
/// subgraphs, there could exist may different theoretical valid (if not always efficient) plans
Expand All @@ -723,7 +723,7 @@ pub struct QueryPlannerDebugConfig {
/// debug a specific issue (with unexpectedly slow query planning for instance). Remember that
/// setting this value too low can negatively affect query runtime (due to the use of sub-optimal
/// query plans).
max_evaluated_plans: Option<u32>,
pub max_evaluated_plans: Option<u32>,

/// Before creating query plans, for each path of fields in the query we compute all the
/// possible options to traverse that path via the subgraphs. Multiple options can arise because
Expand All @@ -737,7 +737,7 @@ pub struct QueryPlannerDebugConfig {
/// path's options exceeds this limit, query planning will abort and the operation will fail.
///
/// The default value is None, which specifies no limit.
paths_limit: Option<u32>,
pub paths_limit: Option<u32>,
}
#[cfg(test)]
mod tests {
Expand Down

0 comments on commit 4c89f5c

Please sign in to comment.