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

refactor(ext/io): move tty metadata to separate collection #18959

Merged
merged 5 commits into from
May 2, 2023

Conversation

dsherret
Copy link
Member

@dsherret dsherret commented May 2, 2023

This removes the tty stuff that's hanging on the file resources and instead stores them in a separate TtyModeStore. Although this will cause the tty store items to not be removed when the resource is removed, I think this is ok to do because there will be a small number of resources this is every done with and usually those resources won't ever be closed.

I'm working on creating a FileResource instead of StdFileResource and I think it's better for the concept of tty metadata to exist separately on top in runtime/ops/tty.rs

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

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

LGTM, I agree these should live in tty.rs

@dsherret dsherret merged commit adcda4f into denoland:main May 2, 2023
@dsherret dsherret deleted the remove_metadata_std_file_resource branch May 2, 2023 21:55
levex pushed a commit that referenced this pull request May 4, 2023
This removes the tty stuff that's hanging on the file resources and
instead stores them in a separate `TtyModeStore`. Although this will
cause the tty store items to not be removed when the resource is
removed, I think this is ok to do because there will be a small number
of resources this is every done with and usually those resources won't
ever be closed.
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