-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recent fix to indexing enums causes not all enums to be indexed #175
Comments
Also in this example the enum in the
|
reverting to |
I think this may be a case of 'unfix the bug, we need the bug'. Technically the new behavior is correct, because the property named However the bug that exists in So, I think the solution here, is the same as the circular references approach. The option to include properties named But you can flip a bit in the Index Config or via a method to ignore that check and revert back to the pre bugfix behavior. Thoughts? |
So I don't think we were relying on a bug. Ie we are calling The properties and components above called "enum" still contain enum schemas that we would expect to be found in the index |
OK, I will loop back around on this, more intelligence on deciding what is and is not an enum is needed. |
fixed |
The change here #169 caused some of our tests to start failing as all the enums we were expecting to be in the index are no longer in the index.
For example in this spec:
The enum in the component named
enum
is not contained within the index anymoreThe text was updated successfully, but these errors were encountered: