Reformat line wrapping in documentation (aws#112)

Reformatted line wrapping of documentation to 80 characters. Also updated changelog to move features to the top and bug fixes to the bottom and used code fences and appropriate indenting where applicable.

Author: andreachild

CHANGELOG.md

@@ -16,50 +16,88 @@ permissions and limitations under the License.
 
 ## Release v1.2.0 (Release Date: TBD)
 
-This release contains new support for Apollo Server integration.
-
-### Bug Fixes
-
-* Don't cast integers to floats in Neptune schema ([#62](https://github.com/aws/amazon-neptune-for-graphql/pull/62))
-* Fix query from AppSync with an empty filter object ([#61](https://github.com/aws/amazon-neptune-for-graphql/pull/61))
-* Retain numeric parameter value type when creating open cypher query ([#63](https://github.com/aws/amazon-neptune-for-graphql/pull/63))
-* Fixed bug with ID argument type conversion and added Apollo arguments to help menu ([#74](https://github.com/aws/amazon-neptune-for-graphql/pull/74))
-* Upgraded axios and babel versions to fix security warnings ([#90](https://github.com/aws/amazon-neptune-for-graphql/pull/90))
-* Fixed failing integration test by excluding `node_modules` from Apollo zip ([#94](https://github.com/aws/amazon-neptune-for-graphql/pull/94))
-* Fixed enum types in schema to be included in input types ([#95](https://github.com/aws/amazon-neptune-for-graphql/pull/95))
-* Fixed bug where id fields without @id directives are not accounted for ([#96](https://github.com/aws/amazon-neptune-for-graphql/pull/96))
-* Fixed custom scalar types in schema to be included in input types ([#97](https://github.com/aws/amazon-neptune-for-graphql/pull/97))
-* Fixed queries generated from an input schema which retrieve an array to have an option parameter with limit ([#97](https://github.com/aws/amazon-neptune-for-graphql/pull/97))
-* Fixed nested edge subqueries to return an empty array if no results were found (([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
-* Fixed usage of variables with nested edge subqueries (([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
-* Fixed cdk output file to contain previously missing files that were necessary to execute the lambda resolver (([#106](https://github.com/aws/amazon-neptune-for-graphql/pull/106))
-* Fixed resolution of nested variables in selection set arguments (([#108](https://github.com/aws/amazon-neptune-for-graphql/pull/108))
-* Changed resolver to use `graphql` `parse` instead of `graphql-tag` `gql` to avoid stale values due to caching (([#109](https://github.com/aws/amazon-neptune-for-graphql/pull/109))
-
-
 ### Features
 
-* Support output of zip package of Apollo Server artifacts (([#70](https://github.com/aws/amazon-neptune-for-graphql/pull/70)), ([#72](https://github.com/aws/amazon-neptune-for-graphql/pull/72)), ([#73](https://github.com/aws/amazon-neptune-for-graphql/pull/73)), ([#75](https://github.com/aws/amazon-neptune-for-graphql/pull/75)), ([#76](https://github.com/aws/amazon-neptune-for-graphql/pull/76)))
-* Allow filtering using string comparison operators `eq`, `contains`, `startsWith`, `endsWith` (([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
-* Added pagination support through the addition of an `offset` argument in query options which can be used in combination with the existing `limit` (([#102](https://github.com/aws/amazon-neptune-for-graphql/pull/102))
-* Added support for queries with sorting ([#105](https://github.com/aws/amazon-neptune-for-graphql/pull/105))
-
+* Support output of zip package of Apollo Server
+  artifacts ([#70](https://github.com/aws/amazon-neptune-for-graphql/pull/70), [#72](https://github.com/aws/amazon-neptune-for-graphql/pull/72), [#73](https://github.com/aws/amazon-neptune-for-graphql/pull/73), [#75](https://github.com/aws/amazon-neptune-for-graphql/pull/75), [#76](https://github.com/aws/amazon-neptune-for-graphql/pull/76))
+* Allow filtering using string comparison operators `eq`, `contains`,
+  `startsWith`,
+  `endsWith` ([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
+* Added pagination support through the addition of an `offset` argument in query
+  options which can be used in combination with the existing
+  `limit` ([#102](https://github.com/aws/amazon-neptune-for-graphql/pull/102))
+* Added support for queries with
+  sorting ([#105](https://github.com/aws/amazon-neptune-for-graphql/pull/105))
 
 ### Improvements
 
-* Increased graphdb.js test coverage using sample data ([#53](https://github.com/aws/amazon-neptune-for-graphql/pull/53))
-* Saved the neptune schema to file early so that it can be used for troubleshooting ([#56](https://github.com/aws/amazon-neptune-for-graphql/pull/56))
-* Alias edges with same label as a node ([#57](https://github.com/aws/amazon-neptune-for-graphql/pull/57))
-* Cap concurrent requests to get Neptune schema ([#58](https://github.com/aws/amazon-neptune-for-graphql/pull/58))
-* Honour @id directive on type fields ([#60](https://github.com/aws/amazon-neptune-for-graphql/pull/60))
-* Changed lambda template to use ECMAScripts modules ([#68](https://github.com/aws/amazon-neptune-for-graphql/pull/68))
-* Add template file missing from packaging ([#71](https://github.com/aws/amazon-neptune-for-graphql/pull/71))
-* Separated graphQL schema from resolver template ([#79](https://github.com/aws/amazon-neptune-for-graphql/pull/79))
-* Added unit tests for resolver and moved resolver integration tests to be unit tests ([#83](https://github.com/aws/amazon-neptune-for-graphql/pull/83))
-* Set limit on the expensive query which is retrieving distinct to and from labels for edges ([#89](https://github.com/aws/amazon-neptune-for-graphql/pull/89))
-* Added distinct input types for create and update mutations ([#93](https://github.com/aws/amazon-neptune-for-graphql/pull/93))
-* Enabled mutations for the Apollo Server ([#98](https://github.com/aws/amazon-neptune-for-graphql/pull/98))
-* Refactored integration tests to be less vulnerable to resolver logic changes ([#99](https://github.com/aws/amazon-neptune-for-graphql/pull/99))
-* Enabled usage of query fragments with Apollo Server ([#103](https://github.com/aws/amazon-neptune-for-graphql/pull/103))
-* Compressed resolver schema file and moved schema initialization outside of event handlers to improve performance ([#111](https://github.com/aws/amazon-neptune-for-graphql/pull/111))
-* Updated and proofread outdated documentation ([#107](https://github.com/aws/amazon-neptune-for-graphql/pull/107))
+* Increased graphdb.js test coverage using sample
+  data ([#53](https://github.com/aws/amazon-neptune-for-graphql/pull/53))
+* Saved the neptune schema to file early so that it can be used for
+  troubleshooting ([#56](https://github.com/aws/amazon-neptune-for-graphql/pull/56))
+* Alias edges with same label as a
+  node ([#57](https://github.com/aws/amazon-neptune-for-graphql/pull/57))
+* Cap concurrent requests to get Neptune
+  schema ([#58](https://github.com/aws/amazon-neptune-for-graphql/pull/58))
+* Honour @id directive on type
+  fields ([#60](https://github.com/aws/amazon-neptune-for-graphql/pull/60))
+* Changed lambda template to use ECMAScripts
+  modules ([#68](https://github.com/aws/amazon-neptune-for-graphql/pull/68))
+* Add template file missing from
+  packaging ([#71](https://github.com/aws/amazon-neptune-for-graphql/pull/71))
+* Separated graphQL schema from resolver
+  template ([#79](https://github.com/aws/amazon-neptune-for-graphql/pull/79))
+* Added unit tests for resolver and moved resolver integration tests to be unit
+  tests ([#83](https://github.com/aws/amazon-neptune-for-graphql/pull/83))
+* Set limit on the expensive query which is retrieving distinct to and from
+  labels for
+  edges ([#89](https://github.com/aws/amazon-neptune-for-graphql/pull/89))
+* Added distinct input types for create and update
+  mutations ([#93](https://github.com/aws/amazon-neptune-for-graphql/pull/93))
+* Enabled mutations for the Apollo
+  Server ([#98](https://github.com/aws/amazon-neptune-for-graphql/pull/98))
+* Refactored integration tests to be less vulnerable to resolver logic
+  changes ([#99](https://github.com/aws/amazon-neptune-for-graphql/pull/99))
+* Enabled usage of query fragments with Apollo
+  Server ([#103](https://github.com/aws/amazon-neptune-for-graphql/pull/103))
+* Compressed resolver schema file and moved schema initialization outside of
+  event handlers to improve
+  performance ([#111](https://github.com/aws/amazon-neptune-for-graphql/pull/111))
+* Updated and proofread outdated
+  documentation ([#112](https://github.com/aws/amazon-neptune-for-graphql/pull/107), [#107](https://github.com/aws/amazon-neptune-for-graphql/pull/112))
+
+### Bug Fixes
+
+* Don't cast integers to floats in Neptune
+  schema ([#62](https://github.com/aws/amazon-neptune-for-graphql/pull/62))
+* Fix query from AppSync with an empty filter
+  object ([#61](https://github.com/aws/amazon-neptune-for-graphql/pull/61))
+* Retain numeric parameter value type when creating open cypher
+  query ([#63](https://github.com/aws/amazon-neptune-for-graphql/pull/63))
+* Fixed bug with ID argument type conversion and added Apollo arguments to help
+  menu ([#74](https://github.com/aws/amazon-neptune-for-graphql/pull/74))
+* Upgraded axios and babel versions to fix security
+  warnings ([#90](https://github.com/aws/amazon-neptune-for-graphql/pull/90))
+* Fixed failing integration test by excluding `node_modules` from Apollo
+  zip ([#94](https://github.com/aws/amazon-neptune-for-graphql/pull/94))
+* Fixed enum types in schema to be included in input
+  types ([#95](https://github.com/aws/amazon-neptune-for-graphql/pull/95))
+* Fixed bug where id fields without @id directives are not accounted
+  for ([#96](https://github.com/aws/amazon-neptune-for-graphql/pull/96))
+* Fixed custom scalar types in schema to be included in input
+  types ([#97](https://github.com/aws/amazon-neptune-for-graphql/pull/97))
+* Fixed queries generated from an input schema which retrieve an array to have
+  an option parameter with
+  limit ([#97](https://github.com/aws/amazon-neptune-for-graphql/pull/97))
+* Fixed nested edge subqueries to return an empty array if no results were
+  found ([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
+* Fixed usage of variables with nested edge
+  subqueries ([#100](https://github.com/aws/amazon-neptune-for-graphql/pull/100))
+* Fixed cdk output file to contain previously missing files that were necessary
+  to execute the lambda
+  resolver ([#106](https://github.com/aws/amazon-neptune-for-graphql/pull/106))
+* Fixed resolution of nested variables in selection set
+  arguments ([#108](https://github.com/aws/amazon-neptune-for-graphql/pull/108))
+* Changed resolver to use `graphql` `parse` instead of `graphql-tag` `gql` to
+  avoid stale values due to
+  caching ([#109](https://github.com/aws/amazon-neptune-for-graphql/pull/109))

CODE_OF_CONDUCT.md

@@ -1,4 +1,7 @@
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+
+This project has adopted
+the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see
+the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 opensource-codeofconduct@amazon.com with any additional questions or comments.

CONTRIBUTING.md

@@ -1,59 +1,78 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
-documentation, we greatly value feedback and contributions from our community.
-
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
-information to effectively respond to your bug report or contribution.
+Thank you for your interest in contributing to our project. Whether it's a bug
+report, new feature, correction, or additional documentation, we greatly value
+feedback and contributions from our community.
 
+Please read through this document before submitting any issues or pull requests
+to ensure we have all the necessary information to effectively respond to your
+bug report or contribution.
 
 ## Reporting Bugs/Feature Requests
 
-We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+We welcome you to use the GitHub issue tracker to report bugs or suggest
+features.
 
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
-reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+When filing an issue, please check existing open, or recently closed, issues to
+make sure somebody else hasn't already reported the issue. Please try to include
+as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
 * The version of our code being used
 * Any modifications you've made relevant to the bug
 * Anything unusual about your environment or deployment
 
-
 ## Contributing via Pull Requests
-Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+Contributions via pull requests are much appreciated. Before sending us a pull
+request, please ensure that:
 
 1. You are working against the latest source on the *main* branch.
-2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
-3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+2. You check existing open, and recently merged, pull requests to make sure
+   someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your
+   time to be wasted.
 
 To send us a pull request, please:
 
 1. Fork the repository.
-2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+2. Modify the source; please focus on the specific change you are contributing.
+   If you also reformat all the code, it will be hard for us to focus on your
+   change.
 3. Ensure local tests pass.
 4. Commit to your fork using clear commit messages.
-5. Send us a pull request, answering any default questions in the pull request interface.
-6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+5. Send us a pull request, answering any default questions in the pull request
+   interface.
+6. Pay attention to any automated CI failures reported in the pull request, and
+   stay involved in the conversation.
 
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+GitHub provides additional document
+on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
-
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
 
+Looking at the existing issues is a great way to find something to contribute
+on. As our projects, by default, use the default GitHub issue labels (
+enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at
+any 'help wanted' issues is a great place to start.
 
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
-opensource-codeofconduct@amazon.com with any additional questions or comments.
 
+This project has adopted
+the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see
+the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+opensource-codeofconduct@amazon.com with any additional questions or comments.
 
 ## Security issue notifications
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
+If you discover a potential security issue in this project we ask that you
+notify AWS/Amazon Security via
+our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
+Please do **not** create a public github issue.
 
 ## Licensing
 
-See the [LICENSE](./LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](./LICENSE.txt) file for our project's licensing. We will ask
+you to confirm the licensing of your contribution.