NFS Mount not showing in Windows Explorer

Question

Is there any way to use one handler for input? Let's say I have 10 inputs, and at the moment each of them changes, their contents need to be written in one state, how can I do this? To not use 10 states

	const [inputValue, setInputValue] = useState([]);
  
  const onHandleInput = e => {
setInputValue(e.target.value);
  };

  <label>Sex:</label>
  <select onChange={onHandleInput}>
    <option>Info</option>
  </select>

    <label>First name:</label>
  <input type="text" onChange={onHandleInput} />
  
    <label>Last name:</label>
  <input type="text" onChange={onHandleInput} />
  
    <label>E-mail:</label>
  <input type="text" onChange={onHandleInput} />

<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.6.3/umd/react.production.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.6.3/umd/react-dom.production.min.js"></script>

Solution

I stumbled upon this question just now, because I experienced the exact same problem - and managed to solve it! Although probably uninteresting for OP after several month, others may benefit.

If you mount NFS shares from an elevated command prompt (Run as administrator), the mount will not show up in the explorer running with normal user privileges. The solution is to unmount the share and remount it, either from explorer or from an ordinary command prompt. Admin privileges are not required for NFS mounts.

Comments

[Oberst]

7 Ultimate. I guess I thought that would have been implied since to my knowledge, Ultimate and Ultimate N are the only 2 that can use the NFS service.

[Mxx]

What happens if you try to mount that nfs share directly from Windows Explorer's 'map network drive'?

[Oberst]

Actually, not quite. I just tried to mount as a network drive as V, and it worked fine, after it was mounted as W in cmd. Could that potentially be the problem? Should I mount it as Z in cmd next time and mount as a network drive the letter I want? O_o

[warmachine]

this is a way ,if you give id to your input fields ,it will be a cleaner way ,check my code above once

[ellertsmari]

@warmachine yes and it would work if you have only one instance of the component on your page but if you have more than one you have a problem with your ids because id should be a unique value

[warmachine]

just like you add numbers differently ,ids can be different too and ,if you use the same logic in different component ,it does not matter if your id in component is same as the id in other component,the variables you are creating is only component scope ,unless you redux ,then it can cause problem,but still you can differentiate based on your container

[muasif80]

Thank you. This is a great insight.