What's stopping the error exception from showing up on the client side?

Question

What's stopping the error exception from showing up on the client side?

Here's the scenario: I have an action method called SavePoint that contains some logic and throws a System.ArgumentException with the message "Error, no point found".

Additionally, there is an ajax function named saveFeature which makes a GET request to the url "/Feature/SavePoint", sending some JSON data. In case of success, it executes a callback function, and in case of error, it displays an alert with the thrown error.

The issue arises when trying to display the exception message "Error, no point found" using the thrownError parameter in the error handler of the ajax call. For some reason, thrownError turns out to be empty. Any thoughts on why the error message is not being displayed properly?

javascript c#ajax model-view-controller

Answer 1

Answer №1

Jaromanda X and Brett Caswell provided an explanation for the "why" in their comments. Here is another way to approach it:

public IActionResult SavePoint(PointRequest point)
{
    try
    {
        //some logic
    }
    catch (Exception ex)
    {
        return BadRequest("Error, no point found");
    }
}

Alternatively, you can show the specific error message to the user:

public IActionResult SavePoint(PointRequest point)
{
    try
    {
        //some logic
    }
    catch (Exception ex)
    {
        return BadRequest($"Error, no point found. Message: {ex.InnerException.Message}");
    }
}

Answer 2

Jaromanda X and Brett Caswell provided an explanation for the "why" in their comments. Here is another way to approach it:

public IActionResult SavePoint(PointRequest point)
{
    try
    {
        //some logic
    }
    catch (Exception ex)
    {
        return BadRequest("Error, no point found");
    }
}

Alternatively, you can show the specific error message to the user:

public IActionResult SavePoint(PointRequest point)
{
    try
    {
        //some logic
    }
    catch (Exception ex)
    {
        return BadRequest($"Error, no point found. Message: {ex.InnerException.Message}");
    }
}

What's stopping the error exception from showing up on the client side?

Answer №1

Similar questions

Discover the array of results by implementing a while loop in JavaScript

What is the best way to utilize getInitialProps specifically during the building process of a NextJS site?

Integrate CSS and Javascript Plugins into your Ruby on Rails application

Click the button to automatically generate a serial number on the form

Converting an array into an object using Typescript and Angular

Clicking on a React Material UI ListItem

Is there a way to keep a div element anchored at the top of the page until I reach the bottom and then have it stick to the bottom as I continue

Using JavaScript build-in functions in a Vue template allows for enhanced functionality and

Unable to display Flask jsonify in HTML using AJAX

Error encountered: Unable to access undefined properties while attempting to make an API call to AirTable using NextJS version 13.4

What could be causing the absence of any displayed content in FirBug when typing in the Google Search box?

Ways to apply the DirectCast operator within a specific data type

A step-by-step guide on accessing a JSON configuration file and configuring the parameter for AJAX requests

Problem with transitioning to a different page on Next.js

Utilizing Async/Await with an Unassigned Object

Automatically fill in a text box with previously saved information

An issue occurred while serializing or deserializing, specifically with the JavaScriptSerializer and

Invoke a component and initiate a click event from within the App.vue component

Forget the function once it has been clicked

React Hamburger Menu not working as intended