Repository: oppia/oppia

Issue:
No error message on using an invalid exploration ID in story editor
**Describe the bug**
In the sotry editor, if we try to use an invalid exploration ID for a chapter, although the save draft button remains disabled there is no error message/warning being displayed. 

**To Reproduce**
Steps to reproduce the behavior:
 1. Create a topic
 2. Go to topic editor and click ‘Create Story’, enter a title and go to the editor
 3. Go to story editor
 4. Create a chapter
 5. Add 999 in the exploration ID box and click on save.

**Observed behavior**
There is no error message or warning saying that the entered exploration ID does not exist.

**Expected behavior**
At least an error message indicating that the entered exploration ID is incorrect should be displayed. 

**Screenshots**
![No error](https://user-images.githubusercontent.com/6338799/72117093-62531600-331a-11ea-99d2-d10d8988c16b.png)

**Additional context**
I got this issue as part of release 2.8.9 testing. For more detailed steps, please follow "User logs in, creates and edits a story." section in [this](https://docs.google.com/document/d/1T3HyMU8cMvXY1tyzs801Zgf5oSxLqaHICUH_YZJa4JM/edit#) doc.

No error message on using an invalid exploration ID in story editor
**Describe the bug**
In the sotry editor, if we try to use an invalid exploration ID for a chapter, although the save draft button remains disabled there is no error message/warning being displayed. 

**To Reproduce**
Steps to reproduce the behavior:
 1. Create a topic
 2. Go to topic editor and click ‘Create Story’, enter a title and go to the editor
 3. Go to story editor
 4. Create a chapter
 5. Add 999 in the exploration ID box and click on save.

**Observed behavior**
There is no error message or warning saying that the entered exploration ID does not exist.

**Expected behavior**
At least an error message indicating that the entered exploration ID is incorrect should be displayed. 

**Screenshots**
![No error](https://user-images.githubusercontent.com/6338799/72117093-62531600-331a-11ea-99d2-d10d8988c16b.png)

**Additional context**
I got this issue as part of release 2.8.9 testing. For more detailed steps, please follow "User logs in, creates and edits a story." section in [this](https://docs.google.com/document/d/1T3HyMU8cMvXY1tyzs801Zgf5oSxLqaHICUH_YZJa4JM/edit#) doc.



Discussion:
@anmolshkl I believe if you hover over the warning symbol on the edit icon (the pencil) in the top bar, a list of errors, including the invalid exploration ID, will be displayed
I'm removing from blocking bugs since having to hover over the pencil icon to see the error is normal behavior. However, I agree that this could be made more clear, so I'm leaving this issue open.
@U8NWXD oh, I see. I fear that it is too subtle and easy to miss for creators, so we should change it (happy to know what other creators think). I think it's fine to remove this from blocking bugs while keeping it open.
I agree with @anmolshkl there should be something like  of pop up option , Maybe just an error alert on the lower right side of the application.
is this still unsolved ?
@anmolshkl I believe if you hover over the warning symbol on the edit icon (the pencil) in the top bar, a list of errors, including the invalid exploration ID, will be displayed
I'm removing from blocking bugs since having to hover over the pencil icon to see the error is normal behavior. However, I agree that this could be made more clear, so I'm leaving this issue open.
@U8NWXD oh, I see. I fear that it is too subtle and easy to miss for creators, so we should change it (happy to know what other creators think). I think it's fine to remove this from blocking bugs while keeping it open.
I agree with @anmolshkl there should be something like  of pop up option , Maybe just an error alert on the lower right side of the application.
is this still unsolved ?

Resolving patch:
diff --git a/scripts/check_frontend_coverage.py b/scripts/check_frontend_coverage.py
--- a/scripts/check_frontend_coverage.py
+++ b/scripts/check_frontend_coverage.py
@@ -125,6 +125,7 @@
     'exploration-editor-page.constants.ts',
     'exploration-features-backend-api.service.ts',
     'exploration-html-formatter.service.ts',
+    'exploration-id-validation.service.ts',
     'exploration-init-state-name.service.ts',
     'exploration-param-changes.service.ts',
     'exploration-player-page.constants.ajs.ts',


Test patch: