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

QUEST - reading and editing the Octane Guides preview #588

Closed
jenweber opened this issue Mar 12, 2019 · 27 comments
Closed

QUEST - reading and editing the Octane Guides preview #588

jenweber opened this issue Mar 12, 2019 · 27 comments
Labels

Comments

@jenweber
Copy link
Contributor

jenweber commented Mar 12, 2019

Hello! Thanks in advance for your help! While Octane isn't officially released, and won't be for a while, we are providing a "preview" period where adventurous devs can try it out, and they need guides documentation! A lot of work has already been done, so at this stage, we are looking for people to read the draft of the Octane guides and help us fix errors and fill in the blanks. Can you help us polish things up? Word choice doesn't matter much, so if you see stylistic improvements, please open an issue instead of including them in a PR. However spelling, typo fixes, and and factual accuracy are very important and we would love your help with those.

All work should be done by branching from octane in this repository, and all PRs should be pointed at octane, not master. See #583 for ideas of what to look for, and links to a script that will aggregate code blocks, if that is useful to you. Thank you!!!

If you can help, please comment on this issue to say which page within the guides you can review. In your comment, post a link. When you have a PR, in the description please link to this issue.

List of pages that may need volunteers

(read comments below to see if they are taken)

the-beacons-are-lit

@muziejus
Copy link
Contributor

I can do getting started and services, if that's ok?

@jenweber
Copy link
Contributor Author

Thank you! I updated the list with your work!

@muziejus
Copy link
Contributor

I'll do the testing section next.

@betocantu93
Copy link
Contributor

I can do components section

@mixonic
Copy link
Contributor

mixonic commented Mar 13, 2019

I'm going through "templating" right now. We will see if I am on track!

@dennismende
Copy link
Contributor

I will do Data Management and Ember Data till Friday.

@richard-viney
Copy link
Contributor

I'll review the "Working with JavaScript" section.

@kgautreaux
Copy link
Contributor

I have submitted a PR for "tracked-properties" so I can claim that post-hoc.

rwjblue added a commit that referenced this issue Mar 15, 2019
#588 Reading of "Getting Started" and "Services"

Co-authored-by: Robert Jackson <me@rwjblue.com>
jenweber pushed a commit that referenced this issue Mar 15, 2019
* Refactor MU filenames

* add dots for easier reading
@jenweber jenweber pinned this issue Mar 15, 2019
@mixonic
Copy link
Contributor

mixonic commented Mar 15, 2019

I'm also doing a read through components this morning, mostly with an eye toward using actions consistently as described in #598 (comment).

tl;dr is:

  • On native class glimmer components, ember components, and controllers use the @action decorator and the element modifier {{action this.actionMethod}} passing the method.
  • On classic .extend( ember components and controllers use the actions: { hash and the {{action element modifier {{action 'actionName'}} passing the action name. This usage is no different than best practices today.

mixonic added a commit that referenced this issue Mar 15, 2019
@richard-viney
Copy link
Contributor

@mixonic Re. recommended action syntax, I've been a little uncertain on recommended practice of late, as there appears to be no need to use the action helper unless you want to add arguments to the invocation. i.e. you can do @action onClick() {} in the component and then just onclick={{this.onClick}} in the template with no use of the action helper at all. Also if you write {{action this.onClick}} in the template then you don't actually need the @action decorator at all. The latter form does require the this. prefix though.

I wonder if we're effectively double-binding the function by using both the @action decorator as well as the action helper together with this. .. ?

@mixonic
Copy link
Contributor

mixonic commented Mar 15, 2019

@richard-viney Please read the comment I linked to above for a more complete description of what we're suggesting for best practice and why. If you still have questions please find me in #st-octane on Discord.

🙏 I'm happy to discuss this topic but lets try to keep comments for this quest issue focused on the work at hand. 🍻

@muziejus
Copy link
Contributor

muziejus commented Mar 15, 2019

"Core Concepts", url: "core-concepts" - needs an updated image

I'll make a new image this weekend.

locks added a commit that referenced this issue Mar 17, 2019
…iew-non-mu-file-paths

#588 - octane - guides update - non MU file paths
locks added a commit that referenced this issue Mar 17, 2019
…iew-customizing-serializers

#588 - octane - guides update - model/customizing-serializers
@balinterdi
Copy link

I'd like to do the following from the ED section:

  • Defining Models", url: "defining-models"
  • "Finding Records", url: "finding-records"

@balinterdi
Copy link

I just realized these were done by @efx already (as mentioned by @dennismende above). Shouldn't they be checked out?

jenweber added a commit that referenced this issue Mar 18, 2019
@mike-north
Copy link
Contributor

I'm going through computed-properties now

@lisaychuang
Copy link

lisaychuang commented Mar 18, 2019

I'll be adding comments to issue #633 as I go through the guides, so far I've gone through:

"Getting Started", url: 'getting-started'

  • "Quick Start", url: "quick-start"
  • "Installing Ember", url: "index"
  • "Core Concepts", url: "core-concepts"

"Anatomy of an App", url: "anatomy-of-an-app"

  • "Overview", url: "index" (this section is blank)

@jenweber
Copy link
Contributor Author

Hey team, thanks so much for all your help! We are aiming to freeze the guides tonight, and will pick up work again after the keynote. Please make sure to rebase whatever you are working on, as some big sweeping updates just went in for spellchecks, code block accuracy, etc. I will review and hopefully merge any PRs that are open right now before the end of day.

Y'all are the best and I can't wait to show this off at EmberConf this week ❤️

@jenweber
Copy link
Contributor Author

@dennismende to answer your questions:

  • We are skipping data management for now
  • It is unclear whether link-to will be available in angle brackets for the preview, so let's leave as curly braces for now

We got quite a few updates in for the Routing section today - let me know if you have any to add! Thank you!

@mixonic
Copy link
Contributor

mixonic commented Mar 18, 2019

Ah, I see we won't land anything tomorrow. I'm going to take on "Configuration", and if I can get that tucked away I'll take another pass at the most important bits even if they already got 👀

@jenweber
Copy link
Contributor Author

I'm going to keep working to merge existing PRs tomorrow morning, so for those of you who already got your work PR'd, it will make it in :)

If others like @mixonic still have time to jump in & help, reviewing other people's PRs and doing code suggestions for typos is helpful! I'm going to sleep now so I will catch y'all tomorrow. This is all super good and we are in excellent shape!

@jenweber
Copy link
Contributor Author

Thanks everyone for your help! As of EmberConf 2019, we reached MVP for the Octane Guides 🎉

Anyone who wants to see the outcomes can visit https://emberjs.com/editions/octane for the preview guides. Octane isn't yet in a stable release of Ember - this is a preview - but we are in really good shape for when it's time to ship! And now, more people can try it out and share their feedback. Awesome work, everyone!

@jenweber jenweber unpinned this issue Mar 27, 2019
jenweber added a commit that referenced this issue Apr 6, 2019
jenweber added a commit that referenced this issue Apr 6, 2019
#588 - octane - guides update - model/relationships
@NotGrm
Copy link

NotGrm commented Sep 26, 2019

I just saw a duplicated paragraph in tutorial, here is the PR to fix it https://github.com/ember-learn/super-rentals-tutorial/blob/master/src/chapters/07-reusable-components.md

lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
* Refactor MU filenames

* add dots for easier reading
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
lenoraporter pushed a commit to lenoraporter/guides-source that referenced this issue Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests