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 link to hierarchy in IO doc and fix grammar error #166

Merged
merged 2 commits into from Mar 21, 2018
Merged

Add link to hierarchy in IO doc and fix grammar error #166

merged 2 commits into from Mar 21, 2018

Conversation

Avasil
Copy link

@Avasil Avasil commented Mar 20, 2018

I'm reading docs and encountered small grammar error in IO section.

I also have suggestion to add link to the hierarchy - it is mentioned but it isn't anywhere near and if someone (like me) starts reading docs from the top they will see it much later.

@codecov-io
Copy link

codecov-io commented Mar 20, 2018

Codecov Report

Merging #166 into master will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #166     +/-   ##
=========================================
- Coverage   90.11%   89.92%   -0.2%     
=========================================
  Files          47       47             
  Lines        1002     1002             
  Branches       78       78             
=========================================
- Hits          903      901      -2     
- Misses         99      101      +2

@@ -107,7 +107,7 @@ def fib(n: Int, a: Long = 0, b: Long = 1): IO[Long] =
}
```

`IO` implements all the typeclasses shown in the hierarchy. Therefore
`IO` implements all the typeclasses shown in the [hierarchy](https://typelevel.org/cats-effect/typeclasses/). Therefore
Copy link
Member

Choose a reason for hiding this comment

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

This is pretty cool, but personally I prefer relative links. So either:

../typeclasses/

Or (this being Jekyll):

{{ site.base_url }}typeclasses/

(I'm pretty sure this construct must have a shortcut, but I don't know it)

In the docs I actually used the former. If you move the files, the links break, but then again files should not be moved that often ... cool URLs are URLs that don't change 🙂

Copy link
Author

Choose a reason for hiding this comment

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

I went with the former to be consistent

@alexandru alexandru merged commit a09f171 into typelevel:master Mar 21, 2018
@Avasil Avasil deleted the io-doc-hierarchy-suggestion branch September 8, 2018 09:43
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

4 participants