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
Having a look at the schemas offered for github_issues.csv and github2_pull_requests.csv I find misleading the description of the field body which is Body of the issue/comment.
The description would be more clear with something like Body of the comment. It would be nice to look for the same "error" in other schemas and to fix it.
The text was updated successfully, but these errors were encountered:
Having a look at the schemas offered for github_issues.csv and github2_pull_requests.csv I find misleading the description of the field body which is Body of the issue/comment.
From what I inferred, the description Body of the issue/comment. could be read as "body of the issue or comment". Is this what you would like to point out?
From what I remember, github2 is mainly for comments, but I think it enriches the issue items too but not just the comments. Well, I have to check and re-confirm it tho. In that case, I think the current description fits well. WDYT?
The description would be more clear with something like Body of the comment. It would be nice to look for the same "error" in other schemas and to fix it.
If the data has both issues data and issue comments data, then the current description looks fine. But if it only produces the comments data, I think it is better to replace it with Body of the issue comment. or Body of the pull request comment.
Having a look at the schemas offered for github_issues.csv and github2_pull_requests.csv I find misleading the description of the field
body
which isBody of the issue/comment.
The description would be more clear with something like
Body of the comment
. It would be nice to look for the same "error" in other schemas and to fix it.The text was updated successfully, but these errors were encountered: