-
Notifications
You must be signed in to change notification settings - Fork 45
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
Show top level dir #4165
Show top level dir #4165
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
5f54f14
to
397203f
Compare
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.
Just on change please, but this is great
I'm gonna add a PR description for posterity |
03140df
to
78ea2cb
Compare
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.
Thanks for looking into my question and partially addressing it. I wish there were a better standard way to coerce a React Node to a series of strings for accessible names, but we can address this in a follow-up with an accessibleName
ModelingPaneProps item
Show the top-level project directory name in the title bar of the file tree