Clarification on Overlap Between ExceptionType and WarningType in Aspose.Cells

Aspose.Cells Product Family
,
1

Dear Aspose Support Team,

While working with Aspose.Cells, I came across an overlap between the ExceptionType and WarningType. Specifically, I noticed that both classes have similar or seemingly duplicate codes for certain issues. For example:

  • FORMULA: Invalid formula.
  • INVALID_DATA: Invalid data.
  • INVALID_OPERATOR: Invalid operator.
  • IO:
    • ExceptionType: “The file is invalid.”
    • WarningType: “The file is corrupted.”
  • LIMITATION: Out of MS Excel limitation error.
  • FILE_FORMAT vs. UNSUPPORTED_FILE_FORMAT:
    • ExceptionType: Invalid file format.
    • WarningType: Unsupported file format.

Questions:

  1. Overlap in Codes: Using PdfSaveOptions.setIgnoreError(true) often allows recovery from issues by generating warnings instead of terminating the process. This makes ExceptionType and WarningType seem to perform very similar roles. Why are there duplicate or overlapping codes between these two classes? Is there a specific reason for maintaining this separation when their behavior appears to overlap?

  2. Precedence and Conditions: In case a specific issue arises (e.g., an invalid formula or unsupported file format), which of the two (ExceptionType or WarningType) takes precedence? Are there specific conditions or thresholds under which one is triggered instead of the other?

Understanding the distinction and expected behavior will greatly assist in gracefully handling various scenarios in my application. I appreciate any clarification or documentation you can provide on this matter.

Thank you for your time and support.

Best regards.

2

@l.alex

Could you please specify what specific information or documentation you are looking for regarding the overlap between ExceptionType and WarningType in Aspose.Cells?

3

@l.alex,

Your observations about the overlap between ExceptionType and WarningType in Aspose.Cells are valid, and it’s insightful to recognize that both of these categories seem to address similar issues.
Let us evaluate them in details and then we may guide you on how to handle them in your application. Moreover, we will clarify your queries and concerns too. We will get back to you soon.

4

@l.alex

To eliminate redundancy and ambiguity of those apis, we decided to unify them by replacing WarningType with ExceptionType. In newer versions with the change user just needs to do with ExceptionType for all features.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-57330

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

5

@l.alex,

We are pleased to inform you that your issue (Ticket ID: “CELLSNET-57330”) has been resolved. The fix/enhancement will be incorporated in the forthcoming release (Aspose.Cells v24.12), scheduled for the next week of December 2024. You will be notified once the new version is published.

6

The issues you have found earlier (filed as CELLSNET-57330) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi