Skip to content

Bug Fix: store typescript_declarations config and rebuild if changed (Attempt 2) #4562

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

daniellionel01
Copy link

New branch for bugfix related to #4523

Had a merge commit in my history but I am too scared of messing up my branch with rebasing, because I have no experience with that action.

File changes are identical though

FYI @lpil

Copy link
Member

@lpil lpil left a comment

Choose a reason for hiding this comment

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

Super nice, thank you! Couple small notes inline.

kind: FileKind::File,
path: ts_indicator_path,
err: Some(e.to_string()),
})?;
Copy link
Member

Choose a reason for hiding this comment

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

self.io.write already returns the right error type so can return it as-is without wrapping it in another layer.

Copy link
Author

Choose a reason for hiding this comment

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

Done!

.paths
.build_directory_for_target(self.mode(), self.target());

let ts_indicator_path = build_path.join("typescript-declarations.lock");
Copy link
Member

Choose a reason for hiding this comment

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

This isn't a lock file so let's remove the .lock extension.

Copy link
Author

Choose a reason for hiding this comment

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

Done!

@lpil lpil marked this pull request as draft June 16, 2025 14:06
@daniellionel01
Copy link
Author

@lpil Addressed both comments. Thank you!

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.

2 participants