-
Notifications
You must be signed in to change notification settings - Fork 87
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
Fix for #27 Unwarranted circular property definition #28
Conversation
I'm not sure I understand correctly. |
I meant that is was worth a PR. By the way, I had not time to review it for merging it in my branch. My bad, sorry! |
@@ -81,6 +81,19 @@ public void multipleValuesAreResolved() | |||
} | |||
|
|||
@Test | |||
public void propertyIncludesAnotherPropertyMoreThanOnce() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To match the previous method, wouldn't multipleOccurrencesOfTheSameValueAreResolved
be more appropriate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One of my concerns naming this test was choosing a name that would be as descriptive as possible.
I agree that multipleOccurencesOfTheSameValueAreResolved
is probably grammatically more akin to the other tests.
Then I would suggest multipleOccurencesOfTheSamePropertyWithinAnotherAreResolved
ormultipleOccurencesOfTheSamePlaceholderWithinAnotherAreResolved
as the terms "property" and "placeholder" seem to be used interchangeably within the file, and the thing being resolved to the value is the property/placeholder.
It's hard to name things right, and I do not really have a strong opinion in this case. I'd let the final word on this to @robertotru.bertotru
@psenechal-stingray If I'm not mistaken, that link ...points to here. I'm confused. Also, shouldn't there be a test for not a circular reference (e.g., |
@lpearson05 I'm a bit confused too. As you've probably seen, I do not contribute frequently on GitHub. It looks like comments on the commit of my fork are also shown here, but not the other way around. As for |
...plus minor fix to avoid side effects on ExpansionBuffer::toString