In compatibililty_hints.py, there is a incompatibility_description list that should be removed.
For each flag in the list:
- A better name for it needs to be found, suitable for including in the features structure
- The features list (FeatureSet.FEATURES) should be updated to include it
- The caldav-server-tester project should be fixed to check for it
- Consider if it's possible to create work-arounds in the caldav code making consistent results from the API, regardless of server support. If it's easy, then it should be fixed, if it's not so easy, an issue could be recorded in the issue tracker, if it's very complicated or causes too much overhead, then "nevermind"
- The test code should be amended to use the feature (
self.is_supported(...) or self.skip_unless_support(...)) rather than the incompatibility flag.
- All work needs to be validated by running tests (this means we need to be able to test the code towards incompatible servers to be able to move things).
This is a continuation of #402 - more information can be found there.
It involves quite some work, typically several hours of work for each flag, and there are A LOT of them (though I've killed quie a lot already). I found Claude to be quite helpful at this, though it's needed to review the changes proposed by claude.
In compatibililty_hints.py, there is a incompatibility_description list that should be removed.
For each flag in the list:
self.is_supported(...)orself.skip_unless_support(...)) rather than the incompatibility flag.This is a continuation of #402 - more information can be found there.
It involves quite some work, typically several hours of work for each flag, and there are A LOT of them (though I've killed quie a lot already). I found Claude to be quite helpful at this, though it's needed to review the changes proposed by claude.