วีดีโอ

Thank you

Thank you

You can mail me at tamilskillhub@gmail.com

Thank you

Just check you have added all required annotations. Revisit the video once

Sure. Stay tuned.

Ok thank you

Thanks 🔥

Thank you

Thank you

Thank you 🤗

Will upload soon

Stay tuned

Thank you

Lombok annotations can sometimes have issues, especially if your IDE or build tool is not properly set up to handle them. Here are some common troubleshooting steps to ensure Lombok annotations like @Getter and @Setter work properly: 1. Check Lombok Dependency Ensure that Lombok is correctly added as a dependency in your pom.xml (if using Maven) For Maven, the dependency should look like this: <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>1.18.24</version> <scope>provided</scope> </dependency> 2. IDE Plugin Installation If you're using IntelliJ IDEA: Go to File > Settings > Plugins and search for "Lombok". Install the plugin and restart the IDE. After restarting, go to File > Settings > Build, Execution, Deployment > Compiler > Annotation Processors. Ensure that Enable annotation processing is checked. If you're using Eclipse: Install the Lombok plugin via the Lombok JAR. You can download it from Lombok's official website. Once downloaded, run the JAR (java -jar lombok.jar) and point it to your Eclipse installation. Restart Eclipse.

Sure

Please watch this video - th-cam.com/video/2Z_xrfQUI4A/w-d-xo.html

Sure

Thank you

Sure

i have manually inserted records and specified IDs for them, because of that the auto-increment value might skip to a higher number to avoid conflicts. (Sometimes, if you’ve inserted data manually or via another tool (not through your Spring Boot application), the sequence might have been altered. Make sure to clear any cache if applicable.)

GenerationType.IDENTITY: Always uses the database’s native auto-increment mechanism. The database is responsible for generating the primary key. GenerationType.AUTO: Hibernate decides the best strategy based on the database you are using. This could be IDENTITY, SEQUENCE, or TABLE, depending on the database. In this project i have used AUTO so hibernate will manage the generation of key

Welcome 👍

No because it's a paid version. if need I can provide you some of alternatives for React use netlify and For Node use render.com.

@@tamilskillhub there is freecpanel providers ??

I think no

thank you

Ok I will try

sure noted.

you can reach me at tamilskillhub@gmail.com

Pattern you requested for Email const pattern = /^(([^<>()\[\]\\.,;:\s@"]+(\.[^<>()\[\]\\.,;:\s@"]+)*)|(".+"))@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\])|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/;

Try to use Google login or any other login provider

Sure

You have to use the catch block and get the error

Sure I will

Sure

​@@tamilskillhubalso if possible make a backend for this project in express

Sure

Yeah it's possible. But if you have validated the token then it's not possible. And from the backend you need to perform any operation you have to send the token. If the user set authenticated true then toke will send as undefined and api doesn't send response

Yeah it will create a reference and then it will do the operation. Because of instance each call will be considered as different function.

Try chatgpt or IMDb paid version

Suggest topic if you need. Thank you

@@tamilskillhub microservices

@@tamilskillhub WebSocket

Sure

Sure

Can you provide more details about error?

React.memo is a higher-order component that optimizes performance by memoizing the result of a component's render. It helps in preventing unnecessary re-renders when the component's props haven't changed

You can mail me at tamilskillhub@gmail.com

Check you have added as Role_User like this format.

@@tamilskillhub ROLE_USER, ROLE_MODERATOR, ROLE_ADMIN already I hace used like this format, but Role is not found

Can you view the video once and check the middleware code?

Thank you. Sure

Stay tuned

Yeah from version 18. we don't need Nodemon For example: node --watch your-server-file.js This --watch flag will enable the watch mode, and Node.js will restart the application whenever it detects changes to the files in the project. Keep in mind that this feature is still experimental, so it might not have all the capabilities or stability of Nodemon. If you need more advanced features or stability, you may still prefer using Nodemon.

Thank you

Let's break down the issue step by step and see if we can identify the problem. From your description, it seems like you're doing everything correctly, but the destructured `data` object is not being received as expected. Here's a structured version of your code for clarity: ```javascript // api.js import axios from 'axios'; const api = axios.create({ baseURL: 'localhost:8000', }); export const signup = (parameter) => api.post('/signup', parameter); // signup.js import { signup } from './api'; async function sign(parameter) { try { const { data } = await signup(parameter); console.log(data); // To check what you're receiving } catch (error) { console.error('Error signing up:', error); } } ``` ### Troubleshooting Steps: 1. **Ensure Correct Response Format from Backend:** Make sure your backend is correctly sending the response in the expected format. It should look something like this: ```javascript // Example using Express.js app.post('/signup', (req, res) => { const result = someData; // Replace this with your actual data logic res.json({ result: result }); }); ``` 2. **Check API Endpoint:** Ensure that the endpoint `localhost:8000/signup` is correct and accessible. 3. **Network Issues:** Verify that there are no network issues preventing the response from being received. You can use browser dev tools to inspect the network request and response. 4. **Error Handling:** Ensure that your code handles potential errors gracefully. You might be missing an error message that could give a clue about the problem. ### Debugging Steps: 1. **Inspect the Response:** Modify your code to log the entire response object before destructuring: ```javascript async function sign(parameter) { try { const response = await signup(parameter); console.log(response); // Log the entire response object const { data } = response; console.log(data); // Log the destructured data } catch (error) { console.error('Error signing up:', error); } } ``` 2. **Validate Backend Response:** Double-check the backend to ensure the response is being sent correctly: ```javascript app.post('/signup', (req, res) => { const result = { someData: 'example' }; // Replace this with your actual data logic res.json({ result: result }); }); ``` ### Common Mistakes to Check: - **Typographical Errors:** Ensure that all names and paths are correctly typed. - **Cors Issues:** Ensure CORS is properly configured if your frontend and backend are on different domains. - **Base URL Configuration:** Ensure `baseURL` in your Axios instance is correctly set as `baseURL` and not `baseurl`. ### Example Correction: Here's a more refined version with additional error logging: ```javascript // api.js import axios from 'axios'; const api = axios.create({ baseURL: 'localhost:8000', }); export const signup = (parameter) => api.post('/signup', parameter); // signup.js import { signup } from './api'; async function sign(parameter) { try { const response = await signup(parameter); console.log('Full response:', response); // Log the entire response object const { data } = response; console.log('Destructured data:', data); // Log the destructured data } catch (error) { console.error('Error signing up:', error); } } ``` If these steps don't resolve the issue, please provide more details about the backend implementation and the actual response you're receiving from the API. This will help in diagnosing the problem more accurately. If it resolves your problem. i will be happy. Kudos to Chat-gpt.

Try to change the server using application.properties file. Then start you application

Thank you

Thank you

Thank you

Check jdbc url and password configuration. Ensure the connectivity with database established. Check you have used @Entity annotation