🐛 Bug Report: typing a duplicate email in subscribe section

[saimaheshtaduri]

📜 Description

When I type a email twice, The second time, its showing Oops! something went wrong. Instead there should be a specific error message like "email already subscibed"

👟 Reproduction steps

1. GO to blog
2. navigate to the subscribe section
3. try to give same email twice
4. the second time, its telling, "something went wrong" instead of "email already exists"

👍 Expected behavior

I think, it is better if "email already exists" note arise, when a duplicate email is typed. This makes user understand that he has already subscribed. ( coz first time, I thought the there is network issue and tried disconnecting my internet too )

👎 Actual Behavior with Screenshots

Getting "something went wrong" when duplicate email is typed in subscribe section.

💻 Operating system

Windows

🤖 Node Version

(not applicable )

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

Yes I am willing to submit a PR!

[nevo-david]

Do you want to work on it @saimaheshtaduri?

[saimaheshtaduri]

Yes ! @nevo-david

[nevo-david]

Good luck!!! :)

[saimaheshtaduri]

@nevo-david please review the pr #62

[sachin-duhan]

In case of duplicates do we get a 302 or relevant status code,
if Yes, then displaying "You are already subscribed" would make sense.

To address internet issue, better option is -

// Online state
const [isOnline, setIsOnline] = useState(navigator.onLine);

useEffect(() => {
    // Update network status
    const handleStatusChange = () => {
      setIsOnline(navigator.onLine);
    };

    // Listen to the online status
    window.addEventListener('online', handleStatusChange);

    // Listen to the offline status
    window.addEventListener('offline', handleStatusChange);

    // Specify how to clean up after this effect for performance improvment
    return () => {
      window.removeEventListener('online', handleStatusChange);
      window.removeEventListener('offline', handleStatusChange);
    };
}, [isOnline]);

in other exceptional cases, we can use a default message - "Internal server error / Something went wrong"