Move schema data and support imports

jamie commented

2017-07-17 04:16:43 +00:00

(Migrated from git.hazaar.io)

I have a project where the schema data is causing the schema file to get quite large. Seeing as this is also a single large JSON object, it may be a good idea to be able to break it out into separate files. This would also help with maintenance and protect from possible conflicts in source code management.

I also think that the data should be split out because the data part itself is not version controlled like the rest of the schema.

I have a project where the schema data is causing the schema file to get quite large. Seeing as this is also a single large JSON object, it may be a good idea to be able to break it out into separate files. This would also help with maintenance and protect from possible conflicts in source code management. I also think that the data should be split out because the data part itself is not version controlled like the rest of the schema.

jamie commented

2017-07-18 06:13:06 +00:00

(Migrated from git.hazaar.io)

mentioned in commit fb41660107

mentioned in commit fb41660107cc4b6bf6c0a274e824780951fc05f8

jamie commented

2017-07-18 07:02:34 +00:00

(Migrated from git.hazaar.io)

closed via commit ce06e55e10

closed via commit ce06e55e100e1afc293bbaeecaa74664cf3077e9

jamie commented

2017-07-18 22:05:49 +00:00

(Migrated from git.hazaar.io)

I took out support for the old data element in the main schema.json file. For backwards compatibility, I think this was a bad idea so I'm going to add it back. There is no reason I can't just support both.

jamie commented

2017-07-18 22:05:52 +00:00

(Migrated from git.hazaar.io)

reopened

jamie commented

2017-07-18 22:06:24 +00:00

(Migrated from git.hazaar.io)

added ~161 and removed ~160 labels

jamie commented

2017-07-19 00:21:07 +00:00

(Migrated from git.hazaar.io)

closed via commit fe3a4a092a

closed via commit fe3a4a092a2e0a6acf6b6db83aff87095467f99f

Rows
Columns

Move schema data and support imports #16