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

Update readme to match lib doc #48

Merged
merged 3 commits into from
Jun 6, 2017
Merged

Update readme to match lib doc #48

merged 3 commits into from
Jun 6, 2017

Conversation

chrisppy
Copy link
Member

@chrisppy chrisppy commented Jun 2, 2017

No description provided.

@jameshurst
Copy link
Member

I think the README should provide a brief overview of the library and explanation of what it does, and for detailed usage information that's what the documentation is for. For this reason I'm inclined to say the README is fine as is. What do you think @frewsxcv?

Copy link
Member

@frewsxcv frewsxcv left a comment

Choose a reason for hiding this comment

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

Personally, I'm in favor of having the README be identical (or near-identical) to the top level module docs. There are a couple RFCs open related to this:

On the one hand, it's unfortunate having the duplication, but the second RFC should make it easier to reduce duplication by having the module level documentation just point at the README.md file. I do see why people might want to have minimal docs in the README and just point to the API documentation, but I just happen to prefer having a brief overview of the library in the README. What do you think?

channel.validate().unwrap();
```

### Example
Copy link
Member

Choose a reason for hiding this comment

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

Instead of having two Example sections back to back, you could do something like this if you wanted:

### Examples

Validating a `<channel>`:

'''
<code here>
'''

Validating an `<image>`:

'''
<code here>
'''

@tafia
Copy link
Contributor

tafia commented Jun 4, 2017

I too prefer having the readme very similar to the crate top module documentation.

@jameshurst
Copy link
Member

Fair enough, that's good with me then.

README.md Outdated
rss = { version = "*", features = ["from_url"] }
```

```ignore
Copy link
Member

Choose a reason for hiding this comment

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

This should be ```rust

Copy link
Member

Choose a reason for hiding this comment

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

This should be ```rust,no_run

we we want the Rust syntax highlighting, but we don't want this test to run since it hits the network

https://doc.rust-lang.org/nightly/book/first-edition/documentation.html#running-documentation-tests

Copy link
Member

Choose a reason for hiding this comment

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

though, since these code blocks aren't being tested (since they're in the README), it actually doesn't matter if we no_run or ignore, so yeah, just rust should be fine

README.md Outdated

### Example

```
Copy link
Member

Choose a reason for hiding this comment

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

```rust as well

README.md Outdated

### Example

```
Copy link
Member

Choose a reason for hiding this comment

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

```rust

README.md Outdated

### Example

```
Copy link
Member

Choose a reason for hiding this comment

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

This should be ```rust as well

@frewsxcv
Copy link
Member

frewsxcv commented Jun 6, 2017

This is great, thanks!

@frewsxcv frewsxcv merged commit a6cffbe into rust-syndication:master Jun 6, 2017
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