Sign Up Flow Check LocalStorage Value & UI Project Step Improvement in Mobile Size #9
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
- All the scaffold frontend structure was moved into a `/console` path in order to have full control of the rest. - All founded `href` were properly updated and tested.
- `builder.io` was configured in the project and is now fully integrated to allow anyone control site's content. - Some components were registered to be used, but are more for testing for now.
- Vercel Analytics & SpeedInsights were activated.
- A set of helper interfaces & types were defined. - The hardhat config was modified to use the `ChainlinkUserConfig` Type. - `tsconfig-paths` lib was installed and configured.
- Chainlink contracts were installed. - Compiler version updated to fill chainlink contracts requirements.
- Gateway and GatewayClient interfaces were defined. - Example contracts and deploy scripts were removed.
- The CCGateway was implemented. - Some errors were mapped. - A helper function to get the current network config as a `ChainLinkNetworkUserConfig` type was created. - The deploy Gateway script was configured.
- An Simple GatewayClient contract was created so anyone could easily use the gateway. - The deploy script for the ExampleClient was created. - A final deploy script to grant all clients access to the gateway was created.
- A toolkit for easily manage available functions in the gateway was created.
- The LINK tasks were registered as part of the hardhat env. - A simple task for reading the balance of the deployer account was created. - A set of helper functions for LINK token were created.
- A set of helper functions to manage the subscriptions were created.
- A helper function to automatically upsert the provided scripts in the gateway as requests was created. - It should receive only new scripts and those who needs any update. - minor changes in the deployment scripts to streamline the gateway contract name. - The gateway will be the consumer for each created subscription.
- A new task was registered to use the entire set of tools previously created. - The task will load all the scripts (ie. functions) that needs to be upserted in the gateway, create or fund the subscriptions for each, and finally register the function as a request in the gateway to be used by clients. - Each step of the task uses the current network. - The outcome is a `link_functions_map.json` file that contains the results of these operations and could be used to feed/seed the clients contracts.
- `@chainlink/functions-toolkit` is still using ethers@v5 which have several incompatibilities with the current project ethers@v6. - To resolve this problem, a workaround to generate a `Signer` using ethers@v5 using the current scope was created. - internal `@chainlink/functions-toolkit` ethers lib was mapped as `ethers@v5` to be accessible whenever it's needed. - Some npm scripts were added to easily access the new hardhat chainlink defined tasks.
- Minor change to revert transaction if the subscription id is missed.
- A more accurate name was assigned to the task.
- Minor changes to accept an arbitrary address to fetch balances of. - Native network token balance included.
- The potentially networks to be used for deployment were updated. - All the details required for the scripts were included.
- Polygon Amoy deployment details. - Optimism Sepolia deployment details. - A Base endpoint was declared and deployed.
- The mongo config uri and db name were extracted as ENV vars. - .env.example updated accordingly.
Chainlink Functions | Gateway
…ockmagic-tech-team into personal/allan/onboarding
onboarding workflow - user register API
Simplify Endpoint Deployment and Management in API Gateway
- Minor changes were made to ensure the providers could be included without the need of the layout. - The console layout was extracted and properly implemented. - The SignUp page now implements these providers.
- The input field was updated to use the `AddressInput`. - Minor changes to the `InputBase` and `AddressInput` to allow pass through class styles into the main container.
- Minor bug fixed when user goes back on step 0. - Minor changes to include a tooltip on each circle step hover. - Some code simplification.
- Minor changes to allow the grid of options reflects the current selected option. - Steps that use this were updated.
- The DID was implemented as part of the SignUp process. - The API /user `POST` was moved as a server action to improve security and easier implementation. - The SignUp state is now filling the user to be stored in the DB after performing the DID.
uklok-owner
added a commit
to tippi-fifestarr/Ceptor-scaffold-OP
that referenced
this pull request
Jun 3, 2024
…tation Personal/allan/invitation
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.
Description
The signup flow check if there is any existing value in localStorage, and adjust project step in mobile size .
Additional Information
Your ENS/address: