Dave Shanley f629c0ff58 fix for resolving looping relative references ...

In vacuum, a usecase was reported where an infinite loop occurred due to re-parsing the same reference over and over in a loop. It was re-creatable and it was because the loop happened before the index was ready.

This should be resolved now, at least for this use case. To be sure, I have included the specs as a new test.

https://github.com/daveshanley/vacuum/issues/268
Signed-off-by: Dave Shanley <dave@quobix.com>

2023-05-16 17:03:02 -04:00

..

circular_reference_result_test.go

99.9 % coverage & full OpenAPI v3 support

2022-08-31 10:04:39 -04:00

circular_reference_result.go

feat: Allow circular references when the properties are not marked as required

2023-01-11 05:47:06 -05:00

extract_refs_test.go

updated: a fix for #50

2023-02-27 11:05:18 -05:00

extract_refs.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

find_component_test.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

find_component.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

index_model_test.go

Support for relative links now in place #73

2023-02-22 09:14:27 -05:00

index_model.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

index_utils.go

fix: Issue #82

2023-02-22 09:14:27 -05:00

search_index_test.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

search_index.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

spec_index_test.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

spec_index.go

fix for resolving looping relative references

2023-05-16 17:03:02 -04:00

utility_methods_test.go

Bumped coverage on utility methods

2023-03-06 13:18:28 -05:00

utility_methods.go

Bumped coverage on utility methods

2023-03-06 13:18:28 -05:00