Why is there a need for both Assignee and Assignees in GitHub? -


currently experiment github api, , noticed following: if request issue, has both assignee , set of assignees - same properties user above. feature introduced year ago, seems.

while see reason having assignees, don't understand why have both properties, if, in case of having assignees set, first 1 assignee. why isn't set of assignees enough store information? 1 thing can imagine keeping assignee legacy reasons, other explanation can be?

here example, right on official github page. can see, assignee octocat, , after calling post /repos/:owner/:repo/issues/:number/assignees, assignees octocat , 2 new users.

i haven't seen official rationale github, think it's safe has maintaining api compatibility.

they couldn't change assignee field being single user object being list of user objects since break existing api clients assume single object.

they didn't want bump api version v4 small change that.

so solution add new assignees field, existing api clients still works (although don't assignees) , new code being developed can use new assignees field.


Comments

Popular posts from this blog

php - Permission denied. Laravel linux server -

google bigquery - Delta between query execution time and Java query call to finish -

python - Pandas two dataframes multiplication? -