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

[core] Don't bail out early if docs:api fails #21726

Merged
merged 2 commits into from Jul 9, 2020

Conversation

eps1lon
Copy link
Member

@eps1lon eps1lon commented Jul 9, 2020

Instead of exiting early as soon as a single component crashes yarn docs:api we continue building and list the errors at the end. This ensures that we don't create a big git diff if a single file fails. Ideally I'd get rid of the rimraf to reduce the git noise to a minimum but cleaning up is not that trivial so I'm sticking with the crude approach.

Basically where yarn docs:api would remove the full directory when a single file changes it now only removes the files that failed. Hopefully that helps working with docs:api.

Also did some refactoring to new node APIs.

@eps1lon eps1lon added the core Infrastructure work going on behind the scenes label Jul 9, 2020
@mui-pr-bot
Copy link

mui-pr-bot commented Jul 9, 2020

Details of bundle changes

Generated by 🚫 dangerJS against d2f6c40

@github-actions github-actions bot added PR: out-of-date The pull request has merge conflicts and can't be merged and removed PR: out-of-date The pull request has merge conflicts and can't be merged labels Jul 9, 2020
@oliviertassinari
Copy link
Member

This ensures that we don't create a big git diff if a single file fails.

I have been there too 😆, solving this pain will be appreciated

@eps1lon eps1lon merged commit 8dcb48f into mui:next Jul 9, 2020
@eps1lon eps1lon deleted the docs/docs-api-improve branch July 9, 2020 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants