-
Notifications
You must be signed in to change notification settings - Fork 393
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
feat(ssr-compiler): api decorator support #4766
base: master
Are you sure you want to change the base?
Conversation
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.
We are missing some tests for what happens with @api
when there is a subclass/superclass relationship.
See these Karma tests for some components that we can probably just import wholesale and use for testing.
4f09b90
to
e1dfd53
Compare
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.
Why do we need expected-ssr.html
here? We can't align SSR v2 with engine-server
?
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.
Let's do that in a different PR, I'll create a work item for it.
props = __filterProperties( | ||
props, | ||
new Set(${/*public fields*/ is.arrayExpression}), | ||
new Set(${/*private fields*/ is.arrayExpression}), |
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.
We can move the new Set()
into the helper function to make this a bit cleaner.
Details
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item