Repository navigation
Docs/rc4 cache store - #22
Merged
Merged
Conversation
- Updated the versioning information in various documentation files to reflect the new release (1.0.0rc4). - Clarified backend unreachable error messages in the API server documentation. - Enhanced WebSocket documentation to specify cache store behavior. - Added a new document on bringing your own backend, detailing the custom checkpointer, store, and cache store implementations. - Introduced breaking changes regarding the new BaseCacheStore and its implications for existing configurations. - Updated project statistics to reflect the latest release counts and dates. - Fixed various references to Redis and cache store in troubleshooting documentation. - Added a new release note for the 1.0.0rc4 version, highlighting breaking changes and new features.
…iting - Updated project setup documentation to clarify the differences between Quick Start and Production templates, including changes to authentication and rate limiting options. - Revised rate limiting documentation to reflect the new cache store structure and configuration. - Enhanced WebSocket documentation to specify shared limits in multi-worker deployments. - Adjusted troubleshooting guide to align with new cache store terminology and error messages. - Updated release notes for version 1.0.0rc4 to highlight breaking changes and migration paths related to the new cache store implementation. - Added a new section in the homepage to introduce CLI commands for initializing projects, starting the server, and configuring settings.
…nking block signature issues
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs for 10xgraph and 10xgraph-api 1.0.0rc4. Client stays at 1.0.0-rc.2.
Changes
aping()rules, BaseCacheStore contract, skeleton, contract suite).
cache_storereplaces top-levelredis,rate_limitandtoken_revocationacrossserver, reference, production, concepts, build guides, examples and blog posts.
/health/readydocumentscacheinstead ofredis.10xgraph init(three questions),10xgraph config,10xgraph revoke,id_generatorand
thread_name_generatordocs updated.BaseCheckpointer.aping()in the checkpointer reference and checkpointing guide.(site.ts, homepage, project-stats, installation).
Check
npm run buildpasses.