This repository was archived by the owner on Mar 24, 2026. It is now read-only.
[ci fw-only Kotlin/http4k] Fix JSON structure to stop warnings#3308
Merged
NateBrady23 merged 1 commit intoTechEmpower:masterfrom Feb 20, 2018
Merged
[ci fw-only Kotlin/http4k] Fix JSON structure to stop warnings#3308NateBrady23 merged 1 commit intoTechEmpower:masterfrom
NateBrady23 merged 1 commit intoTechEmpower:masterfrom
Conversation
Contributor
Author
|
Another problem: I'm not seeing Kotlin/http4k in TravisCI as a sub build: https://travis-ci.org/TechEmpower/FrameworkBenchmarks/builds/343541053 |
Member
|
Thanks for this @zloster ! Yeah looks like http4k isn't in the .travis.yml file for some reason. There's a PR open for an upgrade and I'll have it added there. Thanks again for all your contributions! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses a minor point in #3295. And indeed it was annoying :)