Created delete account flow, and add some effects on subscribe button at marketplace #5
Conversation
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
…n in the Google OAuth callback route. This ensures that any cached data related to the user's authentication session is cleared.
The changes involve the following files: • route.ts: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts: The getSwaggerSpec function now accepts a storeToCache parameter, which is used to determine whether the Swagger specification should be stored in the cache. If storeToCache is true, the specification is stored in the cache using kv.set(). • page.tsx: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts (in the v1/me/swagger directory): The getAuthSwaggerSpec function now calls the getSwaggerSpec function with false argument to retrieve the base Swagger specification from the cache. The retrieved base specification is merged with the user-specific Swagger paths and updated with the user's username and other information. Overall, these changes improve the caching and usage of the Swagger specification in the codebase.
…related data. It includes changes to the profile actions and page components, as well as the addition of a new DeleteAccountButtonForm component. The update also includes changes to the logout route to remove active sessions and session cookies. The data module has been updated to include a new function to destroy user accounts and all associated records. Overall, this update enhances the user profile functionality by allowing users to delete their accounts and provides the necessary backend logic to handle the deletion process.
…nctionItem.tsx file. Added state variables isSubscribeLoading and isForkLoading to track loading state. Created onSubscribeToggleHandler and onForkHandler functions to handle the subscribe and fork actions respectively, while updating the loading state. Modified the button elements to show loading spinners when loading. In the MarketplaceFunctionList.tsx file, changed the handleFork and handleSubscribeToggle functions to be asynchronous and return promises. Updated the onFork and onSubscribeToggle callbacks in the MarketplaceFunctionItem component to be async.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chozzz
added a commit
that referenced
this pull request
Nov 24, 2024
chozzz
added a commit
that referenced
this pull request
Nov 24, 2024
… at marketplace (#5) * Added functionality to clear user caches after creating an OAuth token in the Google OAuth callback route. This ensures that any cached data related to the user's authentication session is cleared. * Refactor Swagger configuration and usage in the codebase. The changes involve the following files: • route.ts: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts: The getSwaggerSpec function now accepts a storeToCache parameter, which is used to determine whether the Swagger specification should be stored in the cache. If storeToCache is true, the specification is stored in the cache using kv.set(). • page.tsx: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts (in the v1/me/swagger directory): The getAuthSwaggerSpec function now calls the getSwaggerSpec function with false argument to retrieve the base Swagger specification from the cache. The retrieved base specification is merged with the user-specific Swagger paths and updated with the user's username and other information. Overall, these changes improve the caching and usage of the Swagger specification in the codebase. * This update introduces a new feature to delete user accounts and all related data. It includes changes to the profile actions and page components, as well as the addition of a new DeleteAccountButtonForm component. The update also includes changes to the logout route to remove active sessions and session cookies. The data module has been updated to include a new function to destroy user accounts and all associated records. Overall, this update enhances the user profile functionality by allowing users to delete their accounts and provides the necessary backend logic to handle the deletion process. * Refactored the MarketplaceFunctionItem component in the MarketplaceFunctionItem.tsx file. Added state variables isSubscribeLoading and isForkLoading to track loading state. Created onSubscribeToggleHandler and onForkHandler functions to handle the subscribe and fork actions respectively, while updating the loading state. Modified the button elements to show loading spinners when loading. In the MarketplaceFunctionList.tsx file, changed the handleFork and handleSubscribeToggle functions to be asynchronous and return promises. Updated the onFork and onSubscribeToggle callbacks in the MarketplaceFunctionItem component to be async.
chozzz
added a commit
that referenced
this pull request
Nov 25, 2024
chozzz
added a commit
that referenced
this pull request
Nov 25, 2024
… at marketplace (#5) * Added functionality to clear user caches after creating an OAuth token in the Google OAuth callback route. This ensures that any cached data related to the user's authentication session is cleared. * Refactor Swagger configuration and usage in the codebase. The changes involve the following files: • route.ts: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts: The getSwaggerSpec function now accepts a storeToCache parameter, which is used to determine whether the Swagger specification should be stored in the cache. If storeToCache is true, the specification is stored in the cache using kv.set(). • page.tsx: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts (in the v1/me/swagger directory): The getAuthSwaggerSpec function now calls the getSwaggerSpec function with false argument to retrieve the base Swagger specification from the cache. The retrieved base specification is merged with the user-specific Swagger paths and updated with the user's username and other information. Overall, these changes improve the caching and usage of the Swagger specification in the codebase. * This update introduces a new feature to delete user accounts and all related data. It includes changes to the profile actions and page components, as well as the addition of a new DeleteAccountButtonForm component. The update also includes changes to the logout route to remove active sessions and session cookies. The data module has been updated to include a new function to destroy user accounts and all associated records. Overall, this update enhances the user profile functionality by allowing users to delete their accounts and provides the necessary backend logic to handle the deletion process. * Refactored the MarketplaceFunctionItem component in the MarketplaceFunctionItem.tsx file. Added state variables isSubscribeLoading and isForkLoading to track loading state. Created onSubscribeToggleHandler and onForkHandler functions to handle the subscribe and fork actions respectively, while updating the loading state. Modified the button elements to show loading spinners when loading. In the MarketplaceFunctionList.tsx file, changed the handleFork and handleSubscribeToggle functions to be asynchronous and return promises. Updated the onFork and onSubscribeToggle callbacks in the MarketplaceFunctionItem component to be async.
chozzz
added a commit
that referenced
this pull request
Dec 9, 2024
chozzz
added a commit
that referenced
this pull request
Dec 9, 2024
… at marketplace (#5) * Added functionality to clear user caches after creating an OAuth token in the Google OAuth callback route. This ensures that any cached data related to the user's authentication session is cleared. * Refactor Swagger configuration and usage in the codebase. The changes involve the following files: • route.ts: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts: The getSwaggerSpec function now accepts a storeToCache parameter, which is used to determine whether the Swagger specification should be stored in the cache. If storeToCache is true, the specification is stored in the cache using kv.set(). • page.tsx: The getSwaggerSpec function is now called with a true argument, indicating that the Swagger specification should be stored in the cache. • config.ts (in the v1/me/swagger directory): The getAuthSwaggerSpec function now calls the getSwaggerSpec function with false argument to retrieve the base Swagger specification from the cache. The retrieved base specification is merged with the user-specific Swagger paths and updated with the user's username and other information. Overall, these changes improve the caching and usage of the Swagger specification in the codebase. * This update introduces a new feature to delete user accounts and all related data. It includes changes to the profile actions and page components, as well as the addition of a new DeleteAccountButtonForm component. The update also includes changes to the logout route to remove active sessions and session cookies. The data module has been updated to include a new function to destroy user accounts and all associated records. Overall, this update enhances the user profile functionality by allowing users to delete their accounts and provides the necessary backend logic to handle the deletion process. * Refactored the MarketplaceFunctionItem component in the MarketplaceFunctionItem.tsx file. Added state variables isSubscribeLoading and isForkLoading to track loading state. Created onSubscribeToggleHandler and onForkHandler functions to handle the subscribe and fork actions respectively, while updating the loading state. Modified the button elements to show loading spinners when loading. In the MarketplaceFunctionList.tsx file, changed the handleFork and handleSubscribeToggle functions to be asynchronous and return promises. Updated the onFork and onSubscribeToggle callbacks in the MarketplaceFunctionItem component to be async.
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.