<commit_before>Go-Rest
=======
This contains the Workiva standard REST API client and server implementations for Go.

# Server

The server package contains the APIs for implementing a RESTful web service. The goal is to
provide a framework that makes it easy to build a flexible and (mostly) unopinionated REST API
with little ceremony. It's platform-agnostic, meaning it works both on- and off- App Engine,
and pluggable in that it supports custom response serializers, middleware and authentication.

See the examples to get started.

NOTICE
------
Requirements to commit here:
  
  - Branch off master, PR back to master.
  - [gofmt](http://golang.org/cmd/go/#hdr-Run_gofmt_on_package_sources) your code. Unformatted code will be rejected.
  - Follow the style suggestions found [here](https://code.google.com/p/go-wiki/wiki/CodeReviewComments).
  - Unit test coverage is required.
  - Good docstrs are required for at least exported names, and preferably for all functions.
  - Good [commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) are required.
<commit_msg>Update readme to match new package organization<commit_after>Go-Rest
=======
This contains the Workiva standard REST API client and server implementations for Go.

# Server

This contains the APIs for implementing a RESTful web service. The goal is to provide
a framework that makes it easy to build a flexible and (mostly) unopinionated REST API with
little ceremony. It's platform-agnostic, meaning it works both on- and off- App Engine, and
pluggable in that it supports custom response serializers, middleware and authentication.

See the examples to get started.

# Client

The rest package also contains a client implementation for consuming REST APIs.  It
includes pluggable request authorization and response deserialization.

NOTICE
------
Requirements to commit here:
  
  - Branch off master, PR back to master.
  - [gofmt](http://golang.org/cmd/go/#hdr-Run_gofmt_on_package_sources) your code. Unformatted code will be rejected.
  - Follow the style suggestions found [here](https://code.google.com/p/go-wiki/wiki/CodeReviewComments).
  - Unit test coverage is required.
  - Good docstrs are required for at least exported names, and preferably for all functions.
  - Good [commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) are required.

{'fraction_non_alphanumeric': 0.07914572864321608, 'fraction_numerical': 0.006700167504187605, 'mean_word_length': 4.193478260869565, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '582841', 'n_tokens_mistral': 678, 'n_tokens_neox': 633, 'n_words': 283}