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

[Breaking change] generate getters for needs in pages #1034

Merged
merged 2 commits into from
Mar 7, 2020

Conversation

paulcsmith
Copy link
Member

Closes #853

The breaking change is that you can't use ? in 'needs' anymore. Also we
may overwrite a method by generating a getter but I think there is very
little change since most methods would be defined after needs

Closes #853

The breaking change is that you can't use ? in 'needs' anymore. Instead
we generate a 'getter?' if the type is a Bool. Also we may overwrite a
method by generating a getter but I think there is very little change
since most methods would be defined *after* needs
@paulcsmith paulcsmith changed the title [WIP] [Breaking change] generate getters for needs in pages [Breaking change] generate getters for needs in pages Mar 7, 2020
@paulcsmith paulcsmith merged commit 811a179 into master Mar 7, 2020
@paulcsmith paulcsmith deleted the pcs/853/getters branch March 7, 2020 22:25
@jwoertink
Copy link
Member

wow! This is awesome!

@jwoertink jwoertink added the BREAKING CHANGE This will cause a breaking change label Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BREAKING CHANGE This will cause a breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exposing params via needs is not congruent
2 participants