mirror of https://github.com/jlengrand/helidon.git synced 2026-03-10 08:21:17 +00:00

Files

Romain Grecourt b19f866327 Multipart decoder rework (#2193 )

* MultiPartDecoder implementation update (first pass)

* Fix TCK tests

* fix checkstyle

* update internal doc

* improve indentation

* Fix issue with distinguishing a concurrent onError signal from a concurrent onComplete.

* Incorporate review feedback

* add upstream = CANCELED to cleanup()

2020-07-28 13:30:46 -07:00

application-pom.md

Spec: overview of Helidon Application Poms (#1057 )

2019-09-26 11:39:40 -07:00

config-api.md

Config for Helidon 2.0 (#1102 )

2019-12-05 11:23:29 +00:00

context.md

Alignment of client service APIs between Db and Web Clients. (#1863 )

2020-05-27 14:00:19 +02:00

datachunkinputstream.md

New implementation of PublisherInputStream that improves performance and fixes race conditions (#1690 )

2020-04-27 14:16:05 -04:00

db.md

Helidon DB Client (#657 )

2020-01-23 18:42:21 +01:00

dockerbuild-local-snapshots.md

Application poms (#1022 )

2019-09-12 15:48:09 -07:00

generic-mapping.md

Helidon DB Client (#657 )

2020-01-23 18:42:21 +01:00

generic-type.md

Proposal for generic type mapping. (#204 )

2018-11-19 12:37:17 -08:00

multipartdecoder.md

Multipart decoder rework (#2193 )

2020-07-28 13:30:46 -07:00

protobuf.md

Protobuf support proposal (#280 )

2019-01-02 17:05:07 -08:00

README.md

Create a directory for specifications

2018-11-09 12:15:00 -08:00

README.md

Internal Documents and Specifications

This directory contains internal documents and specifications. These fall into a number of categories:

Guidelines and best practices
Design documents
Feature proposals
Or pretty much anything else

By keeping our documents as source code we can easily find them and easily review them.

Specs vs GitHub Issues

In many cases GitHub issues are sufficient for tracking requirements and basic proposals. But a spec might be more appropriate if you want an easy to review, living document with a fair amount of detail.

Use Markdown

Write your specs in Markdown. AsciiDoc is also OK if you need it.