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

Add "Remove jQuery" guide #64

Merged
merged 6 commits into from
Oct 26, 2018
Merged

Conversation

simonihmig
Copy link
Contributor

Based on RFC 294.

I basically just resubmitted emberjs/guides#2191, which @jenweber already reviewed back then...

@simonihmig
Copy link
Contributor Author

Hm, the failing tests seem to be unrelated! (broken link in defining-a-component.md?)

@jenweber
Copy link
Contributor

@simonihmig the old PR was marked WIP - should this one be merged in or is more work needed?

@simonihmig
Copy link
Contributor Author

I think it should be ok as is. For the old one it was still unclear in which version of Ember the RFC would be implemented, but this is clear now to be 3.3 AFAICT.

@locks
Copy link
Contributor

locks commented May 30, 2018

Weren't we going to have a top-level "Optional Features" section?

@locks locks self-assigned this Sep 23, 2018
@simonihmig
Copy link
Contributor Author

@jenweber @locks I think we should try to get this merged. Open questions:

  • where to put it, under "Managing Dependencies" or some new category ("Optional Features")? If there is no consensus yet, I would suggest to leave it like it is now, and refactor later, otherwise this remains undocumented for too long IMHO.
  • IIRC Ember CLI 3.3 was a republish of 3.2, so Ember CLI 3.4 is the one version that correctly implements the opt out stuff. Should be mentioned probably?
  • this is still targeting the 3.3 docs, should this rather be moved to the current 3.4 docs?

@jenweber
Copy link
Contributor

@locks do you want to find a home for this?

Otherwise I would like to make it a fairly generic url (since urls are forever) and merge.

@jenweber
Copy link
Contributor

Also thanks @simonihmig for your patience. We have let it go too long without a firm decision. The hesitation is that once a url is made in the guides, it becomes something we have to maintain indefinitely, or we break a whole lot of people's urls that point to /release/

@locks locks force-pushed the add-jquery-opt-out branch from fa44a46 to a0858fc Compare September 28, 2018 10:18
@jenweber
Copy link
Contributor

jenweber commented Oct 9, 2018

@locks do you have a decision on where this should go? I suggest we get it in within the next week or so.

This PR was still open as of creating the 3.5 release. This means before this PR to be merged, any changes requested should be made, and then the same additions should be applied to the upcoming 3.5 version files. They will be available later this week. Sorry about the extra step!

@locks locks force-pushed the add-jquery-opt-out branch from a0858fc to 6c9e5dd Compare October 14, 2018 13:18
@locks
Copy link
Contributor

locks commented Oct 14, 2018

I backported to the v3.3 guides since the optional feature was introduced in that release.

@jenweber jenweber self-requested a review October 14, 2018 18:18
@jenweber
Copy link
Contributor

Looks good to me! I would like to hear from @simonihmig before we merge. Thanks @locks!

The Ember framework comes by default with jQuery integration.
It is used for event handling, and to provide some APIs like `this.$()` in components.

With the release of ember-source v3.0.0, an optional feature flag was introduced that allows users to opt out of jQuery.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should be 3.3.0! (also requires Ember CLI 3.4.0 to work properly)

Copy link
Contributor

Choose a reason for hiding this comment

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

hm 🤔


Once you see a feature that you would like to toggle for your project you can run one of two commands, `ember feature:enable <feature>` and `ember feature:disable <feature>`.

Let us disable `template-only-glimmer-components` to see what happens:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

That feature is not listed under the Available features output above. Should we add that?

@locks locks force-pushed the add-jquery-opt-out branch from bfa25a4 to 99053a0 Compare October 26, 2018 20:02
@locks locks merged commit d51344d into ember-learn:master Oct 26, 2018
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.

3 participants