Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
API spec include Korean not transfer microcks
See original GitHub issueI try Microcks with Apicurio.
But create mock is fail.
I guess it was a problem that was Korean marked ???.
when I change Korean to English. create mock is succeed.
please check that transfer file is utf-8 encoding.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Importing Services & APIs | Microcks.io
Import a Postman Collection as a secondary artifact (this artifact will only contribute mocks/examples to the main artifact/spec - Note: API ...
Read more >Microcks 1.3.0 release | Microcks.io
We are so proud and happy to share this new major and important Microcks release two months in advance based on our initial...
Read more >Microcks API
You may use this API from your automation tool to dynamically launch new tests, register new mocks or globally control your Microcks server ......
Read more >Using | Microcks.io
This API will give you visibility on how you use the platform to invoke mocks ... as OpenAPI v2) is still a very...
Read more >Speed-Up Kafka Delivery with AsyncAPI & Microcks - Confluent
In the case of asynchronous APIs, we have the AsynAPI specification to document the endpoints where the schema of the records become the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I use apicurio/apicurio-studio-api:0.2.26 docker image
OK thanks for the feedback. We can file all of this under “UTF-8 Problems” probably.