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

Improve docs for the Router Service #16518

Closed
13 of 27 tasks
jenweber opened this issue Apr 14, 2018 · 21 comments
Closed
13 of 27 tasks

Improve docs for the Router Service #16518

jenweber opened this issue Apr 14, 2018 · 21 comments

Comments

@jenweber
Copy link
Contributor

jenweber commented Apr 14, 2018

The Router Service docs need a more beginner-friendly description. Right now it says:

The Router service is the public API that provides component/view layer access to the router.

I recommend that the "main" description be a PR on its own. This is the file that needs to change.

Ideally the most commonly used APIs should have code blocks demonstrating their use and some explanations of their purpose or how to use them. For example, see EmberArray. Additional PRs could include a code block demonstrating the use of each method or property.

Maintainers may feel free to edit this issue directly. @locks can you mark this help-wanted/new contributors if it looks good to you?

Tasks

  • Methods
  • Properties
    • currentRoute (@sdebarros)
      • explanation (what's a RouteInfo?)
      • code sample (needs usage sample)
    • currentRouteName
      • explanation
      • code sample (needs usage sample)
    • currentURL
      • explanation
      • code sample (needs usage sample)
    • location
      • explanation (should link to different Location types)
      • code sample
    • rootURL
      • explanation
      • code sample (needs usage sample)
  • Events
    • routeDidChange
      • explanation
      • code sample
    • routeWillChange
      • explanation
      • code sample
@jenweber jenweber changed the title Improved docs for the Router Service Improve docs for the Router Service Apr 14, 2018
@Serap08
Copy link

Serap08 commented Nov 9, 2018

Is this issue still open? if yes, I can contribute.

@amanriquez
Copy link

Looking for my first open source contribution, any help needed here?

@locks
Copy link
Contributor

locks commented Jan 26, 2019

@amanriquez definitely! I have updated the original post with a list of what there is to document in RouterService and their current state.
Pick one item and I'll assign you to it :)

@locks locks self-assigned this Jan 27, 2019
@locks
Copy link
Contributor

locks commented Feb 7, 2019

@PrimeN thanks for the help! Please comment with the item you wish to take so we can assign it to you :)

@CDNRae
Copy link

CDNRae commented Feb 12, 2019

Hello! I'd like to contribute to the project by writing up an explanation and code sample for the isActive method.

@locks
Copy link
Contributor

locks commented Feb 12, 2019

@rscotchmer thanks for the help! I'll tag you in the list. Don't hesitate in sending over a work in progress PR if you want some feedback from the team :)

@locks
Copy link
Contributor

locks commented Feb 12, 2019

Hi @Serap08, @amanriquez and @PrimeN, can you pick one item from the task list so I can assign them to you? That way we avoid several people working on the same item!

@CDNRae CDNRae mentioned this issue Feb 15, 2019
@teamdraftbox
Copy link
Contributor

hey @locks im looking to contribute to the above mentioned issue, this is my first time in contributing to a open source, i would like to work on replaceWith method issue, please let me know what exactly is the procedure so i can start working on it

@mschinis
Copy link

mschinis commented Mar 18, 2019

☝️ happy to take transitionTo here, tomorrow at the EmberConf Contributors Workshop

@locks
Copy link
Contributor

locks commented Mar 26, 2019

@Serap08 @amanriquez @PrimeN @mschinis poke poke :)

@teamdraftbox hi, thanks for your interest!
The way to start is:

  1. comment on this thread which part you want to take on (done!)
  2. fork the repository
  3. create a branch with a name of your choosing, for example git checkout -b router-replace-with
  4. open ember.js/packages/@ember/-internals/routing/lib/services/router.ts
  5. add your documentation changes
  6. git commit your changes
  7. push the branch to your github fork
  8. go to your fork on github.com, and you should see a banner telling you to create a new PR. click the create button
  9. wait for our review!

If you need further help, reach out to #dev-ember-learning on the Discord server!

burieberry added a commit to burieberry/ember.js that referenced this issue Mar 27, 2019
@teamdraftbox
Copy link
Contributor

teamdraftbox commented Apr 4, 2019 via email

@madzadev
Copy link

i would love to contribute on this

@locks
Copy link
Contributor

locks commented Apr 29, 2019

@madarsbiss have you picked a specific method/property so I can assign you?

@sdebarros
Copy link
Contributor

✋ I'll take currentRoute for documenting.

@sdebarros
Copy link
Contributor

✋ will be also working on the location property docs

@pauljeannot
Copy link
Contributor

🤚 Took the nice work done by @rscotchmer, and updated it with new class syntax, for the isActive method.

@esbanarango
Copy link
Contributor

Can I take transitionTo code sample? ✋

@locks
Copy link
Contributor

locks commented Oct 26, 2019

@esbanarango hi :) have you sent a PR yet?

@esbanarango
Copy link
Contributor

@locks looks like the code sample was already added here: #18179 We could update the description of this issue. Check code samples for transitionTo, replaceWith and recognize.

@RVMac
Copy link

RVMac commented Oct 28, 2019

Hi, I'm looking to contribute (I'm a beginner BTW). Any task needed to be done?

@locks
Copy link
Contributor

locks commented Jan 10, 2020

Thank you everyone for your help! I believe we have done enough work to close this issue :)

@locks locks closed this as completed Jan 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.