From 8dfc29c48ff580a5b2bc78fea42776e1d85e394e Mon Sep 17 00:00:00 2001 From: John Huddleston Date: Thu, 9 Jan 2020 14:17:32 -0800 Subject: [PATCH] Fix broken link in docs to v2 config JSON schema --- docs/releases/migrating-v5-v6.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/releases/migrating-v5-v6.md b/docs/releases/migrating-v5-v6.md index a9268ef1a..df3360bbd 100644 --- a/docs/releases/migrating-v5-v6.md +++ b/docs/releases/migrating-v5-v6.md @@ -260,8 +260,7 @@ The config file is a JSON file, and as such it's important that everything in yo These can be on a separate line at the very top and very bottom of your file. Syntax is important - if you are getting errors, ensure all your brackets and quotation marks match up, and that commas separate items in the same pair of brackets. -Export v2 config files are generally very similar to export v1, _but there are a few changes_. They are explained in detail below, or you can see [an example of converting a v1 config to v2](#updating-your-config-file). If you are familiar with JSON schemas, we have created one for the new config file [here](https://github.com/nextstrain/augur/blob/v6/augur/data/schema-auspice-config-v2.json). - +Export v2 config files are generally very similar to export v1, _but there are a few changes_. They are explained in detail below, or you can see [an example of converting a v1 config to v2](#updating-your-config-file). For more details, see [the complete JSON schema for v2 config files](https://github.com/nextstrain/augur/blob/master/augur/data/schema-auspice-config-v2.json). Here are the top-level keys of the config JSON in plain English: