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

in docs, improve three-way linking between type and representations #1691

Merged
merged 28 commits into from
Apr 21, 2017

Conversation

danking
Copy link
Contributor

@danking danking commented Apr 18, 2017

No description provided.

@tpoterba
Copy link
Contributor

Why can't I see these changes on the docs artifacts?

@tpoterba
Copy link
Contributor

@danking danking changed the title in docs, improve three-way linking between type and representations Fix all doc warnings and add more detail to Type Apr 19, 2017
@danking
Copy link
Contributor Author

danking commented Apr 19, 2017

First merge: #1693

@danking danking changed the title Fix all doc warnings and add more detail to Type in docs, improve three-way linking between type and representations Apr 19, 2017

.. include:: hailType.rst

- `expression language documentation <types.html#int>`__
Copy link
Collaborator

Choose a reason for hiding this comment

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

I found the transition to the bulleted list confusing.

@@ -0,0 +1,11 @@
This is the representation of and documentation for a Hail type. Values of this
type have two representations: the expression language representation and the
Python representation. This is confusing! There are two sets of documentation
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it helpful to say "This is confusing!"?

type have two representations: the expression language representation and the
Python representation. This is confusing! There are two sets of documentation
for many objects like Variant and Genotype. In methods like
:py:meth:`~hail.VariantDataset.annotate_variants_expr` and
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this is too much. You introduced the two kinds of values, then you went on to discuss various kinds of functions. I would just say there are two kinds of values, in expressions and in Python. Then link to the two kinds. Will also make the transition to the bulleted lists smoother.

@@ -0,0 +1,11 @@
This is the representation of and documentation for a Hail type. Values of this
Copy link
Collaborator

Choose a reason for hiding this comment

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

"This is a Hail type."

@danking
Copy link
Contributor Author

danking commented Apr 20, 2017

@cseed back to you

@cseed cseed merged commit 30016eb into hail-is:master Apr 21, 2017
liameabbott pushed a commit to liameabbott/hail that referenced this pull request May 3, 2017
…ail-is#1691)

* eliminate warning in getting_started.rst

* all warnings are errors

* use anonymous links instead of named links

* fix indentation of list item

* fix a variety of list item syntax issues

* remove illegal excess indentation

* several list item syntax fixes

* variety of list item fixes and a link fix

* remove extraneous character from string [] docs

* favicons must end in ico

* work around a bug in conda

Discussion of issue:

  spatialaudio/nbsphinx#24 (comment)

Root cause:

  ContinuumIO/anaconda-issues#1430

* fix link to tutorial

* fix broken links

* remove broken link to sample

* remove more broken links to sample

* remove references to sec-objects

* fix bad reference syntax

* two small fixes

1. Remove reference to sample
2. Move ico to correct directory

* remove unnecessary html_extra_path entry

* initial attempt

* add missing file

* improve hailType blurb

* further improvements from tpoterba

* Update hailType.rst

* sphinx lists must not have leading space

This triggers an error message:

    Error in "include" directive: no content permitted.

because the one-space-indented text is assumed to be an argument to the
`.. include` directive

Also fix location of hailType.rst

* use anonymous links instead of named links

* simplify docs
@danking danking deleted the improve-doc-links branch December 18, 2019 19:47
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

3 participants