Видео

You will need to store in your db and have maybe firestore rules to allow if user role is equal to admin. You could also do this in your db or both. So the crud methods can have a guard clause in there at the start if user.role !== admin don’t allow (update function for example)

Glad it helped!

I have implemented a check I believe in the playlist that check if they have verified I think but if not then you can do that. It’s been a while since I worked on this but have a look at the docs

Thank you very much!

Thanks for your comment. Maybe will do at some point in the future

Yes why not keep it simple. Or you can use middleware on serverside to determine the branch based on the URL in a switch statement and then pass the props to client and handle brand that way

Glad it helped!

I did this years ago but use the Google sheets api to fetch the sheet data, the sheet should have an id or something. In your app make the get or post call and the you will get the sheet data in json. Once you have that transform the data and render it in your application

In this scenario yes. You have rollup as your module bundler then the benefits of react to have the modularity and ability to use props. There’s no need for next js and that has an express server which you don’t need. With a component library you can host on npm and import into whatever project you are using. Can be next react or anything else then you can add tools such as sanity in your project.

You can import the component that you want to use and with the tree shaking functionality that is the best approach. So you would need to install the entire library to do this

@@imrancodes Thank you

No problem glad it helped

Create a middleware in the server that handles the brand and then pass it down to the client

Thanks for watching!

Thanks, will do!

Thanks a lot

Appreciate it!

Thank you and keep it up

No worries. Glad it helped

Yes I believe its been a while since I used it

you would get the id from the page component and pass it down to the client component as props. const { id } = context.params;

@@imrancodes yes I did it yesterday it took my one whole day to find :) ✌️

Thank you so much Javier. Hopefully it helps you out

Yeah for sure. Thanks for the nice comment and will try and keep more vids coming

Glad it helped!

Glad you enjoyed it!

Its restful

Glad it was helpful!

Glad it was helpful!

Hopefully this video helps you get a better understanding. You just need to build projects with it and stay persistent and you will eventually understand it

I will have a look at this

@@imrancodes Thanks!!!

Hey, I don’t have access to a computer as I am on my holidays but I cannot imagine it being too difficult. Your task should give you guides or information on where the docs are at least. Worst case if you cannot find them then just copy what I have done for the web and say that you improvised as there is no documentation. This will show initiative and show that you found an alternative solution as opposed to doing nothing

Glad it was helpful!

Thank you, I will bare that in mind and glad it helped

It depends on many scenarios. I would say choose what you think is best for your situation

In the scenario you described I would just use the input element props to handle this behaviour of a character count or you can use a form library like react hook form or last resort you can use use state but this will re render your component each time a character is typed

You would just store the key and values in an object and then send that wherever you need to. This can be done with state or ref. Also react hook form is good when working with form data

Glad it was helpful!

These are environment variables that you can save in the circle ci project I recommend doing the release and publish to npm jobs manually

Make sure the url is the same as what you have in the firebase storage so just console.log the url that you are downloading. Also make sure you are uploading correctly as well so again check the video where I do that and check your firebase storage

If you look at video 10 where I log out the errors you can build an error page that you redirect to and output the Errored message. Then you can create a back button to the previous page and a link to the home page

Thanks

This should be fine just follow along the steps. You can always change your eslint config file when it’s created

I think I have done that already in the playlist somewhere have a look through and you will find it

It should be there in the firebase console templates

Glad it was helpful!

No it is not but if you follow along you can create the api yourself and use it :)

Thank you, I will

You can watch this and to hide only for admins you can watch this video in my firebase auth playlist ruclips.net/video/Gq8lOUi1jyw/видео.html

@@imrancodes Thank you imran :>

Yes, you can change the input value using a ref in React. Here's how you can do it: Create a Ref: First, create a ref using useRef() hook or React.createRef(). Attach Ref to Input: Attach the ref to the input element you want to manipulate. Access and Modify Value: Access the current property of the ref to manipulate the input value. Example: import React, { useRef } from 'react'; function MyComponent() { const inputRef = useRef(); // Function to update input value const updateInputValue = (newValue) => { inputRef.current.value = newValue; }; return ( <div> <input type="text" ref={inputRef} /> <button onClick={() => updateInputValue('New Value')}> Set Value </button> </div> ); } In the provided example, inputRef is a ref that points to the input element. The updateInputValue function updates the input value by accessing inputRef.current.value and assigning a new value to it. Remember to handle validations etc I hope this helps :)

@@imrancodes thank you very much. Subbed ❤

You too and thanks for watching!

Hey, It might be a few things: 1. Make sure you are passing in the props to the TodoItem component and console log to see if they are showing up in the todoItem component. 2. I would copy and paste the code in the repo to see if that works as there might be a typo I would just console.log everywhere to see if everything is being passed through correctly and you will find the issue

View Full stack Mern app in description with MongoDB