-
Notifications
You must be signed in to change notification settings - Fork 638
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
refactor(archive): move to single-export files #2958
Conversation
Do we want |
/** @deprecated (will be removed after 0.169.0) TODO: export all once overlapping objects/types are removed */ | ||
export { Tar, type TarData, type TarDataWithSource } from "./tar.ts"; | ||
export * from "./untar.ts"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mod.ts
doesn't exist now. Does it make sense to add these deprecated versions here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, tar.ts
acted as the module entry point. Now that Tar
and Untar
classes have been separated, mod.ts
acts as the entry point for both classes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll also provide a module description where one currently doesn't exist for std/archive
.
hmm both seem having examples:
I'm ok with either way. |
Ok, I'll leave it as is then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is part of #2936, which aims for leaner dependencies and a more straightforward structure by only having one export per file within the archive module.