Issue #10: Fixed invalid property initializations

[alexmerlin]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.66%. Comparing base (ab41082) to head (39f2205).
⚠️ Report is 7 commits behind head on 1.0.

Additional details and impacted files

@@ Coverage Diff @@## 1.0 #11 +/- ##
=========================================
Coverage 96.66% 96.66% Complexity 680 680 =========================================
Files 65 65 Lines 3958 3958 =========================================
Hits 3826 3826 Misses 132 132 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[alexmerlin]

@arhimede It seems that the backwardCompatibilityCheck validator does not allow class properties of type Enum. 🤯

---

The check is triggered when this command runs:

Running roave-backward-compatibility-check --from=1.0 --install-development-dependencies

which uses this package: nikic/php-parser

---

I tried excluding only the two affected files while keeping the BC check in place, but it does not seem to be possible (or I did not find how to do it). Even though the JSON was valid, with my attempts to exclude them, I got:

Error: .laminas-ci.json schema validation failed.

---

We have two options:

• disable the BC check (as it is right now)
• ignore the reported BC break errors (not recommended)
• (Option 3 of 2): keep digging on how to keep both the BC check active and somehow exclude the affected files

[arhimede]

@arhimede It seems that the backwardCompatibilityCheck validator does not allow class properties of type Enum. 🤯

Should you open an issue about that in
https://github.com/Roave/BackwardCompatibilityCheck

* (Option 3 of 2): keep digging on how to keep both the BC check active and somehow exclude the affected files

I agree with option 3