有很多开发者朋友问我有没有类似的前台项目、后台管理项目的种子项目，其实都是类似的，区别在于这些项目需要模版引擎(不建议使用JSP)和静态资源(css、js、img)的支持，稍微调整下即可适用，按照MVC的分层来说的话差异的只是视图层，下面是基于Thymleaf模板引擎的改造步骤，供参考。

1. 加入Thymleaf模板引擎依赖

<dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-thyme

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue? not relevant
• Have you validated the input using an OpenAPI validator (example)? not relevant
• What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

OpenApi 3.0 #340 descriptions are valid CommonMark syntax, currently they are as is to target asciidoc file. However, description content should be converted to asciidoc format from md

为了让 Component 更好, 我设计了这个奖励机制. 凡是满足以下的条件的 bug 都会奖励 25 元的奶茶钱. 钱虽然不多, 重在感谢

Bug 满足条件

• 必须是能复现的
• 必须是 Component 项目中的bug, 不能是其他第三方库的, Idea Plugin 不算在其中. 因为插件属于帮助性的工具, 出问题也不影响你们开发
• 必须是没有其他人反馈过的 Bug
• 必须是我认可的：首先如果真的是 bug, 我不会为了这点钱死皮赖脸不承认. 因为之前看下来, 很多 bug 都是用户自己配置有问题或者代码写的不对引起的, 并不是框架的问题. 所以这个是需要我来判断的. 当然了, 你足够了解 Component 的话, 你自己也会知道到底是不是 Component 的问题

所有发现 bug 受奖励的名单, 会持续更新(

Currently, when we test different transports (tcp, unix socket, etc etc), we run the full test suite:
https://github.com/docker-java/docker-java/blob/21583b51e02c129ead0732fbe235d02eb608e341/.travis.yml#L24-L43

However, it is enough to run a subset that can be affected by changing the transport.

This should dramatically improve the CI times and make it more stable.

We should start using https://github.com/all-contributors/all-contributors to fully recognize the people who contribute to this project, both with code and via answering questions.

Issue
Meager documentation for loadChunk and loadChunkAsync

Explanation
As the title sa

• Framework version: 1.4
• Implementations: Spring Boot 2

Scenario

Using SAM cli pass the alb request
sam local invoke -e alb-post.json

Here is the alb-post.json:
`{
"requestContext": {
"elb": {
"targetGroupArn": "arn:aws:elasticloadbalancing:us-east-2:123456789012:targetgroup/lambda-279XGJDqGZ5rsrHC2Fjr/49e9d65c45c6791a"
}
},
"httpMethod": "POST",
"path":

Currently there is no way to update the pull request with the latest upstream changes, when using the library. Github has provided a REST endpoint for it - https://developer.github.com/v3/pulls/#update-a-pull-request-branch

It will be good use case to add to the library.

Currently we are using unittest (from the stdlib) but the integration is far from perfect. Maybe https://docs.pytest.org/en/latest/ will be a better choice.

From twitter:
https://twitter.com/bbrannic/status/1077892960426041344

The following repo has a good reporting solution which expects the test-run results in JSON format
https://github.com/damianszczepanik/cucumber-reporting

Zerocode already produces test-run results in JSON format.
Some subset of data from this is used for CSV reporting and some for HTML reporting.

Currently it uses _e

From issue #432:

I'd also suggest updating the JavaDoc to better indicate the API behavior: From what I've observed, it only cares about the Date part of the DateSent parameter. (Trying to get the last 30s of messages returns the full day's worth of messages.) I think making a note of that in the JavaDoc would help out new users.

Acceptance Criteria:

1. Reproduce the above behavior
2. Up

Hi I have been trying to make the rest2soap-json example work with another more complex SOAP API. I find it difficult to configure the xsl files with respect to parsing data from JSON body of the request.

It is stated here that the body is directly converted to XML in case appropriate Content-Type head