I wouldn't mind releasing it now as 0.6.0, but I don't think the current state of the code is worthy of a 1.0.0 release.

It needs:

All example and sample projects to run properly (they do not do so now)
Sample projects' dependencies to be brought up to date
Basic tests that exercise each sample project
Basic tests for the core functionality provided
APIApprovals tests added
GitHub Action workflows for tests and publishing
Add code style rules and formatting tests
Review of included public members to see if they are appropriate and do not mirror existing functionality (e.g. MutationInputs is identical to Inputs)
Review of if/how this project would be useful in a typical scenario (with a backing database/repository) versus only for in-memory databases
Basic review of how these classes can interact with the other portions of the published libraries, such as dataloaders or authentication.
Review if connection builders are provided and/or how they interact or conflict with the connection builders provided with the main GraphQL.NET library.
Ensure that the existing documentation is accurate
Ensure that at a minimum, some very basic documentation exists
Preferably, add xml comments to all public members

These are all tasks that should be completed regardless of the feature set provided. None of it is very hard, but it does take time.

I believe that releasing the current code as a 0.6.0 release would allow other developers to test and provide more feedback and/or help to this project.

If this sounds good, I can add in some GitHub Action scripts so it will publish, and we can release 0.6.0 once #88 is merged. I don't have the time to put in the necessary to work on this to bring it to a 1.0.0, and it sounds like @sungam3r doesn't either. So unless someone else volunteers to work on everything that needs to be done, it may be beneficial for the community to release 0.6.0 in the meantime. The currently published 0.5.0 release is useless to anyone, as it depends on GraphQL.NET 0.14.0.633.

Release v1.0.0 #27

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions