-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Not able to traverse more than 1 level of hierarchy #85
Comments
I am having the same problem. Would love for it to work! |
I also have this issue. |
MajorLift
added a commit
to MajorLift/react-component-tree
that referenced
this issue
Nov 24, 2021
- BUG: The unescaped period functions as a wildcard character instead of a plain dot as intended. - Inside a string or template literal, a period preceded by a single backslash (escape sequence) will be parsed as an unescaped period. - The string representation of \. is the double-escaped literal "\\." see also: issue oslabs-beta#85
MajorLift
added a commit
to MajorLift/react-component-tree
that referenced
this issue
Nov 30, 2021
* test 14: Folders as modules / batch exports / barrel files - export * from './File' import { File } from './dir' * test 15: - Variable declaration with.. a) object destructuring alias assignment b) array destructuring - Import Decaration with... * glob import and namespace specifier * See: Issue oslabs-beta#85, oslabs-beta#99
MajorLift
added a commit
to MajorLift/react-component-tree
that referenced
this issue
Nov 30, 2021
- passes test 14 - glob exports in general not yet supported Fixes: Issue oslabs-beta#85 See: Issue oslabs-beta#99
MajorLift
added a commit
to MajorLift/react-component-tree
that referenced
this issue
Nov 30, 2021
- passes test 14 - glob exports in general not yet supported Fixes: Issue oslabs-beta#85 See: Issue oslabs-beta#99
Any update on this? |
I would love to use this extension, but until this is fixed it's not of much use. |
It's been almost a year since anyone has commented on this, but it is still a problem for me today. |
One year later... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Sapling is not able to traverse more than one level of my component tree. I have tried it on several of my projects.
To Reproduce
Steps to reproduce the behavior:
src/App.tsx
I thought maybe this is because the pages are embedded in routes. So I tried the same thing with a single page:
src/Pages/SignUpPage/SignUpPage.tsx
. This is what I got:Note that traversal stopped at TextField, even though there are components under that.
Expected behavior
Full traversal of the component tree.
Screenshots
See above.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: