You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current jekyll site uses a static apis.json file to which new APIs are added by pull request. Because git doesn't understand that a PR's intent is just to add an element to the end of the list, it's really easy to create merge conflicts between unrelated PRs. These need to be manually fixed, and line-by-line fixes on merge conflicts seem like a good vector for mangling data.
I think it would be better if individual API definitions were stored as separate files in a folder that is then combined to form apis.json as part of the jekyll build.
The text was updated successfully, but these errors were encountered:
The current jekyll site uses a static
apis.json
file to which new APIs are added by pull request. Because git doesn't understand that a PR's intent is just to add an element to the end of the list, it's really easy to create merge conflicts between unrelated PRs. These need to be manually fixed, and line-by-line fixes on merge conflicts seem like a good vector for mangling data.I think it would be better if individual API definitions were stored as separate files in a folder that is then combined to form
apis.json
as part of the jekyll build.The text was updated successfully, but these errors were encountered: