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

Added dotnet-corvus-jsonschema #1184

Merged
merged 8 commits into from
May 21, 2024
Merged

Conversation

mwadams
Copy link
Collaborator

@mwadams mwadams commented May 19, 2024

Copy link
Member

@Julian Julian left a comment

Choose a reason for hiding this comment

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

Woohoo! Very nice, thanks, this looks great (though I haven't tried to run it yet).

Left trivial comments, but seems very mergeable!

COPY *.csproj .

COPY . .
RUN dotnet publish -c Release -o /app
Copy link
Member

Choose a reason for hiding this comment

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

It doesn't matter a ton, but you get better Docker layer caching if you do the dotnet restore separately as we do in the other .NET implementation I think.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Interestingly, this doesn't work with a local build for me, so I reverted to a single restore, build, and publish. But I'll have another look now it is functioning.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

OK - I'm a bit stumped as to why this doesn't build!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oh, hang on - it's building on ARM64 for some reason...

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes. It doesn't all blow up on AMD64, but explodes on ARM64.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm not expecting errors.

I'll set it up to preload the metaschema. I don't preload it automatically because you only need it if you need it!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

(Actually that's not strictly true - I'm expecting errors for the datetime leap year tests.)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've taken your changes and added the metaschema as pre-requisites for the test suite.

Let's see what that does...

Copy link
Member

Choose a reason for hiding this comment

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

Sorry you caught me at the exact moment in the middle of some other release-related changes, but think you've got them now.

Copy link
Member

Choose a reason for hiding this comment

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

You pulled in the harness changes but not the .NET workflow special casing. Here, let me simply merge the branch I pointed you at, and then the additional changes can go on top.

@Julian
Copy link
Member

Julian commented May 21, 2024

OK I've merged all your initial commits along with the changes I mentioned to special case .NET onto main, so the only remaining changes (meaning left to be outstanding) should be the ones for the metaschema changes -- it might be easier to do that in a new PR (but I don't care either way personally so will leave this one open for you to close or not).

Thanks again for adding your implementation!

@Julian Julian merged commit 58d7710 into bowtie-json-schema:main May 21, 2024
50 of 52 checks passed
@Julian
Copy link
Member

Julian commented May 21, 2024

Thanks again!

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.

3 participants