Follow-up from "New resource reader capabilities"
The following discussion from !127111 (merged) should be addressed:
-
@nicolasdular started a discussion: (+1 comment) thought (non-blocking): I worry a bit that we introduce another way to serialize resources with the LLM serializers as we already have
IssueSerializer
and API Serializers.It's great that we re-use the
IssueSerializer
already but hoped that we find a declarative way. Initially I was thinking about re-usingAPI::Entities::*
but that doesn't work out (e.g. there is no way right now to include Notes as part of the serialization).For now it's fine, maybe we can come up with something more declarative in the future (I was even thinking about using GraphQL).
Idea from @acroitor:
I do agree with @nicolasdular I think we should move this to an entity that does contain notes. We already have different representations of the issue based on where we need the data, e.g. IssueSidebarBasicEntity
, IssueSidebarExtrasEntity
, IssueBoardEntity
, etc so we can add yet another one for the AI.
I think we need to give it some thought and decide how we want to abstract this, so I'm fine leaving this as is for this iteration and opening a follow-up to discuss, investigate and decide what would be the best way to proceed here, especially as we will potentially have these serializers for other models as well.