feat: Implement ViewMapNotFoundExceptions

[xperiandri]

GitHub Issue : closes #2424

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

Meaningless exception

What is the new behavior?

ViewMapNotFoundException derived exceptions

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

[eriklimakc]

Hello @xperiandri, thanks for the PR! Maybe we could simplify a bit and have something like:

public enum ViewMapSearchType
    View,
    ViewModel,
    Data,
    ResultData

public class ViewMapNotFoundException : Exception

    public ViewMapNotFoundException(ViewMapSearchType searchType, Type? type = null)
        : base(CreateNotFoundMessage(searchType, type))

    public ViewMapNotFoundException(ViewMapSearchType searchType, Type? type, Exception innerException)
        :base(CreateNotFoundMessage(searchType, type), innerException)

    private static string CreateNotFoundMessage(ViewMapSearchType searchType, Type? type)

Or if it's preferable to have multiple exception types (so they can be caught independently), we could define a base exception class like ViewMapNotFoundExceptionBase. In this base class, we can define the CreateTypeNotFoundMessage method such as:

CreateTypeNotFoundMessage(string typeName, Type? type) 
    => $"The {typeName} type {type} was not found in the view registry.";

This method can then be used by the other exception classes that inherit from ViewMapNotFoundExceptionBase. Remember to use the enum ViewMapSearchType, please.

[xperiandri]

I defined a base class.
Type comes from different errors, so different exception types needed

[eriklimakc]

Could you please update your fork with the latest changes from the main repo? It includes an update to the System.Text.Json package to 8.0.4. The previous version 8.0.1 now has vulnerabilities.

[xperiandri]

Repo contributor can rebase my branch onto the latest dev with 2 clicks

[francoistanguay]

Why do we need a specific exception type? I dont see Try/Catch happening on that specific exception type being useful. Couldnt we just have a better error message?

Ideally those discussions would happen at the "specification" level on a discussion first please so there's less back and forth.

[xperiandri]

I will go that way next time

[xperiandri]

So as I mentioned before, if you forget to register some mapping you will see ArgumentException sequence contains no elements. It means nothing to understand what was the issue