-
Notifications
You must be signed in to change notification settings - Fork 30
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
Keep content of textual, unparsed files to the dataset #151
Comments
Should we store all textual files, including ones we parsed? That gives users a consistent capability of being able to analyze any text file (including source). |
The data should be stored into its own data file, not in the AST sequence file. |
There needs to be a Boa function to read the file and return the contents for a given ChangedFile. |
I don't see benefit of storing parsed files because they are already in the asts. |
Agreed. Perhaps limit textual contents to unparsed ASCII files?
|
Parsed files do not retain all information (such as whitespace and comments) however. Hence my thoughts to including them. |
Useful for tasks that processing contents as textual documents.
Users might also write simple parser in Boa to parse and extract information.
The text was updated successfully, but these errors were encountered: