This repository has been archived by the owner on Mar 24, 2020. It is now read-only.
Inheriting specifications #96
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
January 9, 2013 18:46
…tion and use its class. As a fallback, class that declared example if used.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In case we have classes that share similar behavior, it would be nice to specify it only in one place. For example, if we have inherited classes. Connected to issue #88
I think the most natural way is to inherit the specification. To make it work we need a slight modification in the way the context of the example is determined. If we use declaring class of the method, then we incorrectly get parent class. So, first we try to get the class from specification. If it does not exist, we fallback to the class which declared the method.