v3.0.0 #32
Merged
v3.0.0 #32
Conversation
This file contains 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
…and better readability feat(cache): include isCached flag in cache results to indicate cache status refactor(cache): update cache key generation and retrieval to support optional cacheKey configuration refactor(types): modify type definitions to accommodate new cache result structure and optional properties
…ce string for cache and database operations chore(example): comment out optional transformer and cacheKey configurations for simplicity and future reference style(example): improve code readability by formatting and organizing log messages
…event sensitive data from being tracked
…uilding, and testing feat(tests): create unit tests for user operations and cache management chore: add bun configuration file for test coverage reporting fix: update nodemon command to include bun fix for better build process fix: update package.json test script to run bun test for consistency fix: update .gitignore to exclude coverage and environment files fix: remove unnecessary .gitignore from example directory feat(prisma): set up Prisma schema and migrations for user management feat(data): add mock user data for testing purposes feat(functions): implement user management functions with caching capabilities fix: adjust TypeScript configuration to include only source files in compilation
…ove project visibility and maintainability
chore: change pretest command to use prisma migrate instead of generate refactor: update cache type from STRING to JSON in client configuration test: add unit tests for various user operations with different cache types
…bility and maintainability by consolidating cache commands into a single object feat(cacheUncache.ts): implement CacheContext and RedisCacheCommands types for better type safety and clarity in cache operations chore(cacheUncache.ts): remove redundant setCache and getCache implementations to streamline code and reduce duplication fix(cacheUncache.ts): ensure correct handling of cache expiration and stale data logic in getCache function refactor(types.ts): add CacheContext and RedisCacheCommands types to enhance type definitions for caching operations
feat(compose.yaml): add postgres service with configuration for user, password, and database feat(compose.yaml): add latency service to simulate network delay for testing purposes
…ves after a specified time test(staled-cache.test.ts): use delay function in user retrieval test to simulate waiting time before assertion
…stgres services for testing environment fix(ci): modify test step to use local service URIs instead of secrets for easier local testing
…se methods for consistency and clarity fix(cacheUncache.ts): update getCache function to use new method names for Redis commands to ensure proper functionality refactor(types.ts): update RedisCacheCommands type definition to reflect method name changes for better type safety
… settings to enhance readability and maintainability
…es for the project
Feat/cache context
…obs and steps for a more streamlined publishing process feat(publish.yml): change trigger from push to pull_request for better control over when the publish job runs
BREAKING CHANGE: The addition of cache context creates breaking changes
The response returned from prisma is now modified and returned as an
object with the key result in it, which contains the actual result.
- Additionally, this object contains the cache context such as
isCached: Boolean; [True if data returned from cache, else false]
feat(cacheContext)!: Cache Context and More
…package publishing
chore(package.json): add semantic-release to automate versioning and …
…publish workflow to ensure it runs on code pushes to main and next branches
… for better version management
…ches for push and pull requests to improve CI process
…ns for better visibility of package versions
show latest and next npm version in readme, run test on push to dev and pr to all branches
…or dev branch only
chore(test.yml): remove pull_request trigger to streamline workflow
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
No description provided.