ABP Framework is currently referencing the latest version of Select2. However, it appears that there is no active maintenance for the Select2 library at this time. Is there any recommended workaround for this vulnerability, or does the ABP team have plans to replace Select2 with a more actively maintained alternative in future releases?
Our security scan flagged the select2 package issue (CVE-2016-10744, https://nvd.nist.gov/vuln/detail/CVE-2016-10744) in abp/select2 8.0.2. Is there a plan to address or patch this?
Noted, thank you.
there is no docs about this, can support team assist us on this inquiry?
Hello ABP Support Team, I am looking for information about the ABP Framework's End-of-Support (EOS) and End-of-Life (EOL) version list or documentation. Could you please point me to where I can find:
Thank you!
I would like to ask if there's a planned timeline for releasing a version of the ABP Framework that supports .NET 10. We're currently evaluating our upgrade roadmap and would appreciate any information you can share regarding this.
Thanks in advance for your support!
Hi @EngincanV,
noted, I will explore the ExceptionSubcriber. Thank you!
Hi @EngincanV, I understand that I can wrap each endpoint in a try-catch block to handle unexpected errors, but that would be time-consuming for us. Is there a way to centrally handle unexpected errors and return a specific error code and message?
How can I set an error code and override the default generic error message ("An internal error occurred during your request!") for the unexpected exceptions?
{ "error": { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null } }
 
                                