speccy
speccy copied to clipboard
wework
Bringing back reference-component-regex
The resolver is rewriting $refs, so it turns './schemas/parameters.yml#/Page' into '#/paths/~1v1~1conversations/get/parameters/1' and sometimes puts that value into x-miro instead.
We disabled this rule back in #28 to avoid the errors in #23, but we need to get it fixed up proper.
This approach to fixing it tries to use x-miro if its around and $ref is requested, but unfortunately that doesn't seem to work. Seems like $ref is actually rewritten in place without a x-miro to go with it. Sometimes. Dunno why.
Any update on this issue or what's causing it? I see almost the same issue in Widdershins when using the --resolve flag in that tool. https://github.com/Mermade/widdershins/issues/170 was closed, but hasn't fixed our issue. Pointing all refs to #components/schemas/schemaName and then pointing those to the external file isn't feasible for us.
Hey, what is your issue? I think you are mistakenly relating your issue to this pull request, which is adding a rule, not fixing a bug.
The x-miro comments are about how this rule cannot be applied to $ref because it's rewritten. The fact that it's rewritten is not a bug that needs fixing, but this rule (or some of the logic in the rules engine) will need to change to support it.
@MikeRalphson is this something you've looked at in oas-kit? I'd like to bring back reference-component-regex somehow.
Sorry, I probably am mistaken...
I'll submit an actual issue with more details.