Goals and expectations for v0.1

[oguzkocer]

As we are exiting the prototype stage of this project, we wanted to outline some goals and expectations for v0.1 of the library.

Tooling

• All projects - Rust, Kotlin, Swift - are built, tested and linted in CI
• Swift project is published as SPM package
• Kotlin project is published to Automattic's S3 Maven - preferably as a java library instead of an Android one
• Integration test using Docker to run given WordPress version

Approach

• Any implementation is polished and production quality and there is no lingering prototype quality code left from the prototype stage
• One of the WordPress.org REST API endpoints is fully implemented
• Cross platform implementation is fully unit tested

Parsing

• Return strongly typed objects whenever possible Support for different versions of API objects (View, Embed, Edit context parameters) #28
• Separate parsers for different contexts for the same object type

[mokagio]

Also, revisit #32 making the README useful.

[oguzkocer]

We were able to hit most of our goals in this milestone, but we we had to move some of these goals to 0.2. Specifically, we didn't get to clean up the prototype code as much as I'd like, but the new code for /users is close to production quality - with a few caveats. This issue served its purpose as a reference, so I think we are ready to close it.

We also decided to work on the README when we get closer to open sourcing the library - and it seems that'll be after 0.2 the earliest.