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

[Docs] Refine the API reference generation process for libraries #453

Merged
merged 10 commits into from
Apr 17, 2024

Conversation

acezen
Copy link
Contributor

@acezen acezen commented Apr 16, 2024

Proposed changes

related issue #432

  • Add Docs building test to each library CI.
  • Add API reference docs building to README of library.
  • Refine the generation process of cpp, pyspark

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

acezen added 2 commits April 16, 2024 10:00
Signed-off-by: acezen <qiaozi.zwb@alibaba-inc.com>
@acezen
Copy link
Contributor Author

acezen commented Apr 16, 2024

hi, @SemyonSinchenko. The CI report seems that generate GraphAr PySpark docs need to install pyspark first, I'm not sure pyspark is necessary for docs building or not. Maybe I set something wrong? Can you help me with this?

@acezen acezen changed the title Refine the API reference generation process for libraries [Docs] Refine the API reference generation process for libraries Apr 16, 2024
acezen added 3 commits April 16, 2024 10:26
Signed-off-by: acezen <qiaozi.zwb@alibaba-inc.com>
.github/workflows/spark.yaml Outdated Show resolved Hide resolved
.github/workflows/spark.yaml Outdated Show resolved Hide resolved
@SemyonSinchenko
Copy link
Member

SemyonSinchenko commented Apr 16, 2024

hi, @SemyonSinchenko. The CI report seems that generate GraphAr PySpark docs need to install pyspark first, I'm not sure pyspark is necessary for docs building or not. Maybe I set something wrong? Can you help me with this?

Yes, it is needed. Under the hood sphinx, actually imports all the Python files to build a tree. On a stage of the importing all the dependencies should be fulfilled.

Signed-off-by: acezen <qiaozi.zwb@alibaba-inc.com>
@acezen
Copy link
Contributor Author

acezen commented Apr 16, 2024

hi, @SemyonSinchenko. The CI report seems that generate GraphAr PySpark docs need to install pyspark first, I'm not sure pyspark is necessary for docs building or not. Maybe I set something wrong? Can you help me with this?

Yes, it is needed. Under the hood sphinx, actually imports all the Python files to build a tree. On a stage of the importing all the dependencies should be fulfilled.

Thanks Sem, added pyspark install in docs generation process, the CI has passed

run: |
export JAVA_HOME=${JAVA_HOME_11_X64}
pushd java
mvn spotless:check
Copy link
Member

Choose a reason for hiding this comment

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

Maybe let's add --no-transfer-progress in java too? Without that option, it will be much harder to read logs in GitHub actions. I would recommend using that option in every place in CI; that option was introduced for CI builds mostly to make logs readable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Copy link
Member

@SemyonSinchenko SemyonSinchenko left a comment

Choose a reason for hiding this comment

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

LGTM

@acezen
Copy link
Contributor Author

acezen commented Apr 17, 2024

@lixueclaire @Thespica any comments? I prepare to merge the PR today.

@Thespica
Copy link
Contributor

@lixueclaire @Thespica any comments? I prepare to merge the PR today.

LGTM~

@acezen acezen merged commit 50c196d into apache:main Apr 17, 2024
8 checks passed
Elssky pushed a commit to Elssky/incubator-graphar that referenced this pull request Oct 8, 2024
…che#453)


---------

Signed-off-by: acezen <qiaozi.zwb@alibaba-inc.com>
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.

3 participants