Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@mitchknife
Copy link
Contributor

This PR also gets conformance tests up and running. I chose not to create an Express conformance server, but I would think it would be pretty trivial.

Conformance test methods NOT passing for the generated fastify plugin:

  • mirrorBytes
  • mirrorText
  • bodyTypes

I think the failures are due to the generated client not supporting a string body in the http response. It may be an issue with configuring the fastify server as well, I didn't look too closely into yet.

I also wasn't sure how to generate the C# documentation using XmlDocGen.

Preparing to add fastify server impl.
And generate conformance plugin.
- all but three conformance tests are passing (mirrorBytes, mirrorText, and bodyTypes) which will require a bit of work to configurare the fastify server, as well as potential changes to the generated client, which assumes that fetch requests come back with JSON.
- This allows the plugin to live anywhere without needing to know where the client type file is. I debated creating a new type file instead of inlining them in the plugin, but didn't really see a point since it is just for the server to use. Perhaps I'm missing something though...
No longer needed!
- This allows the plugin to live wherever the user wants it to live.
- Ideally I would think the express server should be generated the same way
but that would be a breaking change, so maybe not needed?
As well, we are now running all conformance tests together, testing all client and server code.
@mitchknife
Copy link
Contributor Author

@ejball wanted to make sure this doesn't fall off your radar.

@ejball
Copy link
Contributor

ejball commented Dec 29, 2023

I think the failures are due to the generated client not supporting a string body in the http response.

That sounds right, aka #9.

@mitchknife mitchknife merged commit d17ad41 into FacilityApi:master Dec 29, 2023
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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.