refactor(core): remove deprecated UNSAFE_IFRAME_ATTRS alias#68706
refactor(core): remove deprecated UNSAFE_IFRAME_ATTRS alias#68706erkamyaman wants to merge 1 commit into
Conversation
`UNSAFE_IFRAME_ATTRS` in the `RuntimeErrorCode` enum is a `@deprecated` alias of `UNSAFE_ATTRIBUTE_BINDING` (same value -910) with no usages anywhere. Drop it along with the paired `tslint:disable-next-line:no-duplicate-enum-values` suppression. `RuntimeErrorCode` is re-exported as `ɵRuntimeErrorCode`, so the enum's value set is not a stability commitment.
be6f949 to
d6e763f
Compare
|
Pushed an update: The |
|
Let’s see what @AndrewKushnir thinks. |
@JeanMeche would have the latest info on this (based on an internal discussion). |
|
Since this alias was being renamed. I think we're good to go with the removal of that deprecated entry. (The code is still use in the enum) |
JeanMeche
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
This isn't a Public API change. We're good to go for v22.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
packages/core/src/errors.tsdeclaresUNSAFE_IFRAME_ATTRS = -910in theRuntimeErrorCodeconst enum as a@deprecatedalias ofUNSAFE_ATTRIBUTE_BINDING(same numeric value). It has no usages anywhere in the repo and carries atslint:disable-next-line:no-duplicate-enum-valuessuppression to silence the duplicate-value warning. The alias is also listed ingoldens/public-api/core/errors.api.md.What is the new behavior?
The alias and its paired tslint suppression are removed from
packages/core/src/errors.ts.UNSAFE_ATTRIBUTE_BINDINGstays. The corresponding line ingoldens/public-api/core/errors.api.mdis updated to match.Does this PR introduce a breaking change?