Remove useThemeContext and switch to the new useColorMode added in Canary.

[homotechsual]

Closes #116

[changeset-bot]

⚠️ No Changeset found

Latest commit: f753e33

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

[homotechsual]

Fixes #117

[rohit-gohri]

I will also update the dependencies and then merge this, currently it breaks the build. Thanks for the PR

[tanepiper]

Hi, I'm actually just looking into using this tool and I'm getting this error - when do you think it can be looked at to be merged? We need to serve a lot of OpenAPI docs and this looks like a good tool :)

[edumaciel10]

This it's so good

[slorber]

sorry for the annoyance, maybe we should provide something to make it retrocompatible?

But we'll keep using the theme-common package in the future for such things and use the theme mostly for regular React components

[rohit-gohri]

Merging with failed build, fixing build in this follow up PR: #119
Release should be up soon

[rohit-gohri]

Release is up: #122

[rohit-gohri]

sorry for the annoyance, maybe we should provide something to make it retrocompatible?

@slorber Might be nice, but I'm thinking if we can better declare this dependency b/w plugins<->docusaurus via peerDependencies? I don't currently add Docusaurus as a peer dependency, should I add it? I'm not sure how that would look like

[slorber]

@rohit-gohri now you should add this @docusaurus/theme-common package as a dependency as you use it, so if we do changes on it, you may notice more easily if TS does not compile anymore