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

Dataset isn't in the docs as a "concept #707

Closed
jgeewax opened this issue Mar 12, 2015 · 2 comments · Fixed by #713
Closed

Dataset isn't in the docs as a "concept #707

jgeewax opened this issue Mar 12, 2015 · 2 comments · Fixed by #713
Assignees
Labels
api: datastore Issues related to the Datastore API.

Comments

@jgeewax
Copy link
Contributor

jgeewax commented Mar 12, 2015

We added back the Dataset class (basically an alias class that fills in some blanks for you), but it's not listed on the left navigation of the docs. Any chance we can put that back?

If we do, we should add a lovely ..note: banner on that page saying that if you only interact with one dataset (a default one) that you don't need to worry about this, and you can use datastore.<method> and we'll automatically use the default dataset.


NOTE: @dhermes ported this text over from #708

@dhermes
Copy link
Contributor

dhermes commented Mar 12, 2015

On it.

Secondary bug is that we have no automated way of determining that modules are left out of the api docs. (It's low priority since we seldom add modules.)

@dhermes dhermes self-assigned this Mar 12, 2015
@dhermes dhermes added api: datastore Issues related to the Datastore API. docs labels Mar 12, 2015
@dhermes dhermes added this to the Datastore Stable milestone Mar 12, 2015
@dhermes
Copy link
Contributor

dhermes commented Mar 12, 2015

Filed #714 and sent an easy fix in #713.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: datastore Issues related to the Datastore API.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants