Updated the quickstart to use the new 1.0 API

[cloutiertyler]

Description of Changes

I've renamed the examples/quickstart directory to examples/quickstart-chat for standardization purposes, and also updated the quickstart example project to be in line with the new 1.0 API and the new quickstart guide in the docs: clockworklabs/spacetime-docs#141.

Note that I have also moved the implementation of the example from quickstart-chat to quickstart-chat/client. I felt that this would allow for people to have a root directory with client and server. I will note that this is not how https://github.com/clockworklabs/SpacetimeDB/tree/master/crates/sdk/examples/quickstart-chat does it, so I'm open to change it back one level up if that is preferred. We would need to update the tutorial in that case.

API

This is not an API breaking change.

Requires SpacetimeDB PRs

I do not believe it needs any.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 145e818

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@clockworklabs/spacetimedb-sdk@130

commit: 667c0fc

[gefjon]

Note that I have also moved the implementation of the example from quickstart-chat to quickstart-chat/client. I felt that this would allow for people to have a root directory with client and server. I will note that this is not how https://github.com/clockworklabs/SpacetimeDB/tree/master/crates/sdk/examples/quickstart-chat does it, so I'm open to change it back one level up if that is preferred. We would need to update the tutorial in that case.

I would prefer not to have the server code duplicated in a bunch of different places. I would much prefer that each client SDK repo contain only its client code, with a README linking to the module code in the main SpacetimeDB repository. Failing that, I would accept CI jobs which verify that the module code is line-for-line equal in the two repos. I want to avoid a situation (which we've been in several times in the past) in which each repo defines its own "quickstart-chat" module, with all the versions being different and mutually incompatible.

[cloutiertyler]

I would prefer not to have the server code duplicated in a bunch of different places. I would much prefer that each client SDK repo contain only its client code, with a README linking to the module code in the main SpacetimeDB repository. Failing that, I would accept CI jobs which verify that the module code is line-for-line equal in the two repos. I want to avoid a situation (which we've been in several times in the past) in which each repo defines its own "quickstart-chat" module, with all the versions being different and mutually incompatible.

Whoops! Apologies, that was supposed to be removed, not changed. Fixed.