Gaurav

Hi @ekarademir, I’ve gone through the **issue** and reviewed the current comparison behavior. My understanding is that inherited properties, like **aProperty**, are being flagged as removed because the analyzer uses...

ok @ekarademir, I am on it soon will update you here. Thanks for your Response.

@ekarademir `includeInherited` Option - **What it does:** Controls whether to include inherited properties when comparing models. **Two Options:** `includeInherited: false (Default)` Only looks at properties directly written in each model...

Hi @ekarademir, I have raised a PR to fix the inheritance comparison bug (issue #1067). The implementation adds an `includeInherited` option to the CompareConfig, allowing users to consider inherited properties...

sure @ekarademir Is this looks good: feat(compare-config): add optional includeInherited property and apply it to comparison logic according to the commit conventions. let me know if still any change required.

Hey @DenserMeerkat & @animator !! I noticed the issue where hitting the API locally returns multiple rows/objects in the response. I’d like to work on this — I’ll start by...

Hi @mariobehling ! I've read through this issue and I understand the problem you've reported. ## Issue Confirmed You're absolutely right - this is a real issue in the Eventyay...

@mariobehling I have reproduce the bug Working on Fix.

BUG is Fixed, Raising PR in [sometime...] 1. **Template Fixes**: Display "—" (em dash) instead of "None" in list vi and detail view headers 2. **Form Fix**: Handle `None` email...

@mariobehling , PR is up for review. Please take a look when you have a moment and let me know what you think.