Page MenuHomeElementl

[docs] Dagster GraphQL Python Client [4/4]

Authored by sidkmenon on Apr 19 2021, 6:35 PM.
Referenced Files
Unknown Object (File)
Fri, May 12, 12:59 PM
Unknown Object (File)
Apr 7 2023, 1:11 PM
Unknown Object (File)
Apr 1 2023, 11:39 AM
Unknown Object (File)
Mar 18 2023, 7:36 PM
Unknown Object (File)
Mar 11 2023, 12:36 AM
Unknown Object (File)
Feb 28 2023, 11:51 AM
Unknown Object (File)
Feb 27 2023, 2:09 PM
Unknown Object (File)
Feb 14 2023, 11:00 AM

Diff Detail

R1 dagster
Lint Not Applicable
Tests Not Applicable

Event Timeline

sidkmenon held this revision as a draft.

Adding docs snippets & api docs scaffolding

Trying some stuff with dagster-graphql.rst but still not working :/

Adding API docs and rough skeleton of documentation - just needs a bit of fleshing out

Adding some more description to docs

sidkmenon edited the summary of this revision. (Show Details)

Some return types and raises here are not formatted properly. Could you fix the docstrings?

I also think the GraphQL client deserves its own page in the docs, rather than interpolating the new information in the existing GraphQL API page - any thoughts on this @sandyryza @yuhan @sashank?

This revision now requires changes to proceed.Apr 21 2021, 6:24 PM
sidkmenon edited the summary of this revision. (Show Details)

Refactoring the dagster GraphQL client to its own docs page

Restructure docs to have same format as other pages (Relevant APIs, Overview, Examples, etc)

This revision now requires changes to proceed.Apr 22 2021, 8:20 PM
sandyryza added inline comments.

keep newline plz


I don't feel strongly either way, but I don't think these paragraphs of justification are really necessary. Ultimately it boils down to that many people are more comfortable writing Python than GraphQL, right?


Maybe worth mentioning whether all the GraphQL methods are available in Python or just a subset?

sidkmenon marked 2 inline comments as done.

Responding to @sandyryza's comments

sidkmenon added inline comments.

shortened this section a bit for clarification - the reason it was here was to emulate the docs structure for configured, etc.

This revision is now accepted and ready to land.Apr 26 2021, 7:30 PM

Reformatting reload_repository_location docs