From e24a1273659ccb41948acca45e81271c367454be Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Wed, 11 Oct 2017 11:04:22 -0400 Subject: [PATCH] Fix list formatting lost in move --- ...262-Technical-Rationale-Report,-October-2017.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Test262-Technical-Rationale-Report,-October-2017.md b/Test262-Technical-Rationale-Report,-October-2017.md index 08f1010..17eba25 100644 --- a/Test262-Technical-Rationale-Report,-October-2017.md +++ b/Test262-Technical-Rationale-Report,-October-2017.md @@ -6,10 +6,10 @@ In the course of this effort, many errors have been found and fixed, or eliminat One of the most pressing issues the project faces is organization and structure. Ensuring that Test262 can be consumed by varying clients is paramount to its relevance—and has been the source of significant feedback which has lead to many issues filed and subsequent improvements made. Examples: -https://github.com/tc39/test262/issues/1202 -https://github.com/tc39/test262/issues/1175 -https://github.com/tc39/test262/issues/1062 -https://github.com/tc39/test262/issues/957 +* https://github.com/tc39/test262/issues/1202 +* https://github.com/tc39/test262/issues/1175 +* https://github.com/tc39/test262/issues/1062 +* https://github.com/tc39/test262/issues/957 Test262 is a test suite used by many different platforms, this is a unique phenomenon, but also a challenge. To maintain the project, and its interoperability, Test262 needs to offer a useful file structure, as well as relevant per-test metadata. This creates two primary challenges: human and machine readability. To address the latter, each test file includes a block of YAML formatted metadata (called “frontmatter”), which provides information that can be used by a test runner to understand how to interpret, execute, and validate the test. Frontmatter documentation is available in the project within [Interpreting](https://github.com/tc39/test262/blob/master/INTERPRETING.md) and [Contributing](https://github.com/tc39/test262/blob/master/CONTRIBUTING.md). Even these files, like all documentation, require maintenance. Test262 recognizes that out of date documentation is a problem and the project is working to fix that. As a step towards improving the documentation, the following will hopefully serve to provide technical clarity. @@ -79,9 +79,9 @@ It's also safe to say the communication on where and how Test262 is used is not Test262 is committed to making the following improvements: -Improve documentation for contributing to the project that improves access for everyone. -Provide a technical rationale document, similar to this report, in the main repository. -Review and refine the test metadata to better serve consumer clients and tooling. +* Improve documentation for contributing to the project that improves access for everyone. +* Provide a technical rationale document, similar to this report, in the main repository. +* Review and refine the test metadata to better serve consumer clients and tooling.