Skip to content

Fails generating documentation using dartdoc 8.3.1 #8455

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

Closed
julemand101 opened this issue Jan 10, 2025 · 4 comments
Closed

Fails generating documentation using dartdoc 8.3.1 #8455

julemand101 opened this issue Jan 10, 2025 · 4 comments

Comments

@julemand101
Copy link

Looks like there are an ongoing issue of generating documentation today. Here are the error from riverpod package:

2025-01-07 20:18:13.369414 WARNING: dartdoc 8.3.1 (/tmp/analyzerCLEPGZ/pub-cache/global_packages/dartdoc/bin/dartdoc.dart-3.6.0.snapshot) failed: LateInitializationError: Field 'objectClass' has not been initialized.

https://pub.dev/packages/riverpod/versions/2.6.1/score/log.txt

This error seems to have got fixed in dartdoc 8.3.2 (https://pub.dev/packages/dartdoc/changelog) with this issue: dart-lang/dartdoc#3947

So suggested fix here would be to make pub.dev to use the newer version of dartdoc without this bug.

CC: @RandalSchwartz

@isoos
Copy link
Collaborator

isoos commented Jan 10, 2025

@julemand101: Thanks for reporting this. Upgrading is not automatic, but we could have this included in a new site release sometime next week.

@JaffaKetchup
Copy link

Is this supposed to be fixed by #8456? If so, can we expect documentation to automatically regenerate soon?

@isoos
Copy link
Collaborator

isoos commented Jan 13, 2025

@JaffaKetchup: If/when a new version of pub.dev is deployed it will automatically regenerate. The deployment should happen sometimes this week, depending on a few factors, hopefully early this week.

@julemand101
Copy link
Author

Looks like it have hit production and Riverpod have gotten regenerated the documentation with dartdoc 8.3.2 successfully, based on recent logs. I will therefore close this issue.

Thanks for fixing this! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants