Unifying File Structure Across Issues, PRs, and Discussions

[Goder-0]

@danbi2990

While working on the #173 PR, I adopted a slightly different structure in the associated PR, as noted in the PR description. Specifically, I applied the following separation:

• database/discussion.rs: Defines the schema struct used for database storage
• graphql/discussion.rs: Defines the response struct returned from GitHub's GraphQL API (used in the GitHub Dashboard)

This differs from how related structures were previously organized in other Issues and PRs.

To improve consistency and clarity across the codebase, I’d like to propose aligning the structure of Issues and PRs with the one used in Discussions. This would help ensure a unified direction for future development and make the codebase easier to navigate.

Would love to hear your thoughts on this!

[danbi2990]

I agree with your suggestion. That's why I approved the #173, to update the structure of Issue and PullRequest in a separate issue.

I believe we can open a new issue once the relevant PRs(#173 and #184) are merged.

[Goder-0]

Thanks for the response. Sounds good!

[danbi2990]

Closing this discussion, see #217 for continuation.