Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update-ndc-spec-0.1.3 #13

Merged
merged 2 commits into from
May 29, 2024
Merged

Update-ndc-spec-0.1.3 #13

merged 2 commits into from
May 29, 2024

Conversation

BenoitRanque
Copy link
Contributor

Update to ndc spec 0.1.3

Note: also updating the sdk version to the same number, is that a good idea?

@@ -1,7 +1,7 @@
[workspace]
resolver = "2"

package.version = "0.1.0"
package.version = "0.1.3"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bumped version from 0.1.0 to 0.1.3, to keep the same version number as the corresponding ndc-spec.

Is this a good idea, should we do something else instead? The thinking is having a single number wil be less confusing.

@@ -50,13 +50,17 @@ impl Connector for Example {

async fn get_capabilities() -> JsonResponse<models::CapabilitiesResponse> {
models::CapabilitiesResponse {
version: "0.1.1".into(),
version: "0.1.3".into(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very unsure about this, I think version is supposed to be the ndc-spec version, is that correct?

@@ -84,6 +84,8 @@ struct TestCommand {
configuration: PathBuf,
#[arg(long, value_name = "DIRECTORY", env = "HASURA_SNAPSHOTS_DIR")]
snapshots_dir: Option<PathBuf>,
#[arg(long, help = "Turn off validations for query responses")]
no_validate_responses: bool,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this flag copied from the ndc-test implementation

@soupi
Copy link
Contributor

soupi commented May 29, 2024

fyi this is the third PR implementing this #11 #12

@BenoitRanque
Copy link
Contributor Author

BenoitRanque commented May 29, 2024

fyi this is the third PR implementing this #11 #12

😂 Oops! We can just merge @paf31 's PR then?

@BenoitRanque BenoitRanque added this pull request to the merge queue May 29, 2024
Merged via the queue into main with commit 266f4db May 29, 2024
8 checks passed
@BenoitRanque BenoitRanque deleted the update-ndc-spec-0.1.3 branch May 29, 2024 15:17
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