Fix comment location marshalling in ClassModule #1529
Merged
+81
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1523
The issue is likely caused by RDoc generating documentation using data from marshal load (used by
ri), which has different types than if the generation happen directly.This code can reproduce the same error:
Similar to other code objects' marshalling behaviour,
ClassModule#comment_location's content type would change before/after marshalling. But it should still be an array of pairs that respond to the same set of methods.This commit also adds documentation about the marshalling behaviour of
ClassModule#comment_location.I don't like the fact that data types & shapes could change before/after marshalling. But changing this design will be a breaking change and require some careful planning. So for now the change it to make sure the type change is less surprising