Closed 2color closed 2 years ago
This is a first go at implementing the discussed solution from https://github.com/ipfs/ecosystem-directory/issues/241.
submissions-to-be-published
json
"
sortNumbers
// in the repo "sortNumbers": { "since": 2017 }, // in airtable json "sortNumbers": [ { "since": 2017 }
Closing in favour of #249
Background
This is a first go at implementing the discussed solution from https://github.com/ipfs/ecosystem-directory/issues/241.
Current state
submissions-to-be-published
view (which filters only records with "Included in directory" checked)json
field, parses and stringifies (to ensure JSON is valid)Bugs and JSON discrepancies (between projects in the repo and airtable)
"
the JSON generated by the automation is broken, e.g. NebulussortNumbers
field is an array of objects in the automation script and generated JSON while being an object in this repo's project