Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/486 I think we have 2 options: 1. reset requirements (a simple `this.requirements = null;`) at the end of mutating methods (`addStep` and `removeStep`) 2. don't cache requirements before `applyStrategies()` The problem with 1 is, that we would have to propagate the reset to all child- and parent-traversals. The problem with 2 is, that if we don't cache requirements while startegies are being applied, why do we cache them at all? Are requirements used at runtime? Thoughts?
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---