Modified assignees field in issue struct for preperation of go-gitea/gitea#1884

[kolaente]

I'm currently implementing go-gitea/gitea#1884, this pr should be merged before the one in the gitea project.

[thehowl]

Wouldn't this break the API?

[kolaente]

Yes. But is there another possibility? These are breaking changes.

[thehowl]

I'd suggest keeping the assignee and having ExtraAssignees, being an array. Assignee will be the first, ExtraAssignees will be the rest.

[kolaente]

Honestly, this sound like a hack, not a proper solution. We could keep Assignee for a limited amount of time (and setting it to something like "This is deprecated. Use Assignees", but I'd prefer not to do this), but if we want to make it clean, we have to delete Assignee in favour of Assignees (array).

[thehowl]

Sure, that sounds more ideal. Although, breaking changes in the API before v2 are a big NO from me.

[lunny]

@kolaente you can add a migration on gitea repository.

[lunny]

And you can keep Assignee as the first assignees for keeping compitable

[kolaente]

Ok, so here's what I do: I'll add Assignees (will be an array) and keep Assignee (single user object). Assignee will contain the first assignee, Assignees will contain all assignees, including the first one.

[kolaente]

Thanks!