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

[Deprecation] renderTemplate and disconnectOutlet methods #19388

Closed

Conversation

patocallaghan
Copy link
Contributor

@patocallaghan patocallaghan commented Feb 9, 2021

Deprecates renderTemplate (RFC 418) and disconnectOutlet (RFC 491)

Taken from the Deprecations list

Task list

renderTemplate

  • Deprecation guide added to deprecations app
  • Deprecation message The usage of 'renderTemplate' is deprecated. Please see the following deprecation guide to migrate.
  • Key: route-render-methods
  • Call to deprecate
  • Fix tests

disconnectOutlet

  • Deprecation guide added to deprecations app
  • Deprecation message: "The usage of 'disconnectOutlet' is deprecated. Please see the following deprecation guide to migrate.
  • Key: disconnect-outlet
  • Call to deprecate
  • Fix tests

/cc @locks

@chancancode
Copy link
Member

There was another draft PR #19187, seems good for you to take over but you may find it helpful to reference that.

@patocallaghan
Copy link
Contributor Author

Thanks @chancancode! I'll do that 🙇‍♂️

Copy link
Member

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

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

Might also need to add the render deprecation here too?

deprecate('The usage of `disconnectOutlet` is deprecated.', false, {
id: 'router-render-methods.disconnect-outlet',
until: '4.0.0',
url: 'TODO',
Copy link
Member

Choose a reason for hiding this comment

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

Should be auto-deployed shortly, so you can grab the URL

url: 'TODO',
for: 'ember-source',
since: {
enabled: '3.26.0',
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
enabled: '3.26.0',
enabled: '3.27.0',

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@rwjblue so isn't the current beta cycle 3.26 when we'd expect this to land?

Copy link
Contributor

Choose a reason for hiding this comment

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

So, beta has already branched away from master. This happens 6 weeks before the beta is released. During those 6 weeks, when we land features on master, they are not by default included in beta - they are targeting the release after beta (e.g. canary).

We can, and sometimes do, patch them into the beta branch (e.g. for bugfixes). For features and deprecations, we approach it on a case-by-case basis, but we tend to avoid it unless there is a good reason and it's not a high risk change. In this case, I think it's reasonable to not backport, so we would be targeting master, which is currently 3.27.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've decided to break the disconnectOutlet deprecation out into #19407. The render and renderTemplate deprecations are taking longer than I expected (lots of tests to fix).

@rwjblue
Copy link
Member

rwjblue commented Mar 2, 2021

@patocallaghan - Where are we at with this one?

@patocallaghan
Copy link
Contributor Author

@rwjblue this can be closed now. Thanks!

@patocallaghan patocallaghan deleted the patoc/rfc-491-418 branch March 2, 2021 23:16
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

5 participants