Gracefully handling unselected tool
Review Request #10064 — Created July 3, 2018 and submitted
If a tool was not selected (i.e. user left the dropdown at "---------") when the user saves the tool, the server would result in an Internal Error.
This was due to the fact that we weren't handling the "empty" case when attempting to get the data from the widget.
Now we handle the empty case, which returns no data.
Create new configuration, or edit config:
- No name + no tool -> both error
- Name + no tool -> tool errorsSelecting a valid tool makes the error go away.
Error is "This field is required."
Description | From | Last Updated |
---|---|---|
Can you flesh out the description some? Without looking at the linked bug I can't tell what this change is … |
david |
- Bugs:
-
-
Can you flesh out the description some? Without looking at the linked bug I can't tell what this change is trying to accomplish. Because the description will turn into the commit message, we want it to explain what the problem was and how this change fixes it.
See https://www.notion.so/reviewboard/Writing-Good-Change-Descriptions-10529e7c207743fa8ca90153d4b21fea for our general guidelines on this.
- Description:
-
~ Gracefully handling unselected tool.
~ If a tool was not selected (i.e. user left the dropdown at "---------") when the user saves the tool, the server would result in an Internal Error.
+ + This was due to the fact that we weren't handling the "empty" case when attempting to get the data from the widget.
+ + Now we handle the empty case, which returns no data.