Skip to content
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(jsii): Validate overriding does not affect optionality #549

Merged
merged 2 commits into from
Jun 24, 2019

Conversation

RomainMuller
Copy link
Contributor

Optionality must remain unchancged when overriding methods and
properties, such that types are pure with respects to Liskov's
substitution.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Optionality must remain unchancged when overriding methods and
properties, such that types are pure with respects to Liskov's
substitution.
@RomainMuller RomainMuller requested a review from a team as a code owner June 24, 2019 14:54
Copy link
Contributor

@eladb eladb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a test that verifies that this is caught between base/derived and abstract-base/derived

@RomainMuller RomainMuller requested a review from eladb June 24, 2019 15:43
@eladb eladb merged commit 8c826c1 into master Jun 24, 2019
@eladb eladb deleted the rmuller/add-optinoality-stability-check branch June 24, 2019 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants