Too many levels of error messages
See original GitHub issuePrerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Running the latest version of Constellation
- Attached the Support Package via
Help
>Support Package
- Checked the FAQs: https://github.com/constellation-app/constellation/wiki/FAQ
- Checked that your issue isn’t already filed: https://github.com/constellation-app/constellation/issues
- Checked that there is not already a module that provides the described functionality: https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories
Description
When running either the Merge Nodes, Merge Transactions, or Select Top N plugins when not all the information required for the plugin has been entered, you will receive error messages and a plugin exception. Perhaps only the 3rd error window should appear or maybe a more meaningful window so that the user can understand what information they didn’t enter properly.
Steps to Reproduce
- Select one of the listed plugins
- Click the “Go” button
Expected behaviour: A window should appear explaining what information the user didn’t enter
Actual behaviour: 2 error windows and an exception appear
Reproduces how often: 100%
Additional Information
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Error Messages: Examples, Best Practices & Common Mistakes
Designing error messages is all about limiting the frustration users feel with your form. If they're too stressed—too much cortisol builds ...
Read more >A Complete Guide and List of HTTP Status Codes - Kinsta
Too many of these errors can also indicate that your site isn't of high quality, possibly lowering your rankings. 300-level codes have a...
Read more >Best 10 Examples And Guidelines For Error Messages
Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of...
Read more >What's in a good error message? | Hacker News
Too many errors on one line (make fewer) ... Timestamp (in utc), log level, guid of the data being processed[1], log message, filename...
Read more >Thoughtful Error Handling - Medium
Many different types of errors, such as buffer overflows, will dump memory for an attacker. More on buffer overflows later.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have reproduced this problem in the debugger to identify where/when these dialogs and exceptions are being thrown. They are:
By removing the ‘e’ from the call the following is what is produced by the LOGGER call:
@formalhaut69 so I had this issue tracked in my internal issues list so I’ve just added to yours and updated the title…hope your ok with that 😄.