AL-FL/client conditionals #9
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Issue Type
Description
Moved 'grabFile' function to parser.js and created 'traverseAST' function to traverse through the given file. Along with 'traverseAST', added conditional functionality to check if node is a client component based on hook usage and 'use client' directive.
FL's contribution for making the 'grabFile' functionality from pulling from his branch.
Previous behavior
We had 'grabFile' function in the panel.js and no function to begin traversing the file.
Expected behavior
We now have functionality to see console logs of conditional checking and the AST's nodes information to extract from.