Skip to content

Feat/docs prerelease#39

Merged
rgommezz merged 16 commits into
masterfrom
feat/docs_prerelease
Aug 20, 2017
Merged

Feat/docs prerelease#39
rgommezz merged 16 commits into
masterfrom
feat/docs_prerelease

Conversation

@rgommezz

@rgommezz rgommezz commented Aug 15, 2017

Copy link
Copy Markdown
Contributor

Closes #31

@rgommezz
rgommezz requested a review from satya164 August 15, 2017 19:26
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 6516b8a on feat/docs_prerelease into 7e1dfa2 on master.

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 6516b8a on feat/docs_prerelease into 7e1dfa2 on master.

Comment thread docs/API.md Outdated
```
* `options?: Options` (optional) - same as `options` in `createMaterialPalette` function.

* `defaults?: PaletteDefaults` (optional) - Global defaults which will be propagated to each _connected_ component, alongside with palette instance, which will be used, if the specific color profile is not found:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Replace : with .

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling b94b361 on feat/docs_prerelease into 7e1dfa2 on master.

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling d7720b5 on feat/docs_prerelease into 7e1dfa2 on master.

@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 6b8a57a on feat/docs_prerelease into 7e1dfa2 on master.

Raúl Gómez Acuña added 2 commits August 16, 2017 16:44
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 758caf3 on feat/docs_prerelease into 7e1dfa2 on master.

@rgommezz

Copy link
Copy Markdown
Contributor Author

@zamotany @satya164 can I merge it?

Comment thread docs/API.md
@@ -1,5 +1,107 @@
# API

## `createMaterialPalette()`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would say to divide this doc into section as I did in withMaterialPalette to:

  • example of usage
  • description
  • syntax
  • flow types
  • arguments
  • more examples (this can be also concatenated with example of usage

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Sorry, but that's your personal opinion about structuring and it's already well structured. The API is thorough and complete. That section doesn't have to follow withMaterialPalette because you did it exactly that way. We don't have any convention in place. Again, this is the first release and I am putting all my effort to make it happen. We can always sit down later and elaborate a plan for structuring docs. So please guys, I am expecting more collaboration and flexibility on your side rather than pointing out every single detail, without enough justification.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why are you so mad reul

@rgommezz
rgommezz merged commit 436e01c into master Aug 20, 2017
@rgommezz
rgommezz deleted the feat/docs_prerelease branch August 20, 2017 10:27
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.

4 participants