Closed SimonHoiberg closed 4 years ago
This task is up for grabs during Hacktoberfest :raised_hands:
If you want to work on this task, please claim it here in the comments. Feel free to ask any questions here as well :blush:
I am wiling to work on this.
Hi @DipanjanDasIT That sounds awesome! I'll assign you right away :smile:
@Silind can we change the spec file format from yaml to RAML?
Can you please stick to YAML format?
Yes, let's stick to YAML format. The change will be too comprehensive at this moment.
Currently
The Twitter API Client is generated based on one single
twitter-api-spec.yml
file which is currently a whopping 3000+ lines long. It's really cumbersome to scroll around in that file to find what you want.Desired
The
twitter-api-spec.yml
file is split up into multiple.yml
files. One for each group.AC
src/spec/
is renamed tosrc/specs/
and all references in the generator files are changed.twitter-api-spec.yml
is split up into multiple files.Additional notes
To begin with, I think it would be great to have one for each group.
A file
src/specs/basics.yml
, a filesrc/specs/accounts-and-users.yml
, a filesrc/specs/tweets.yml
, etc.The file
twitter-api-spec.yml
should still be the main spec file that references these other files.