-
Notifications
You must be signed in to change notification settings - Fork 9
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
add ability to specify a specific file to write results to too #67
Conversation
i think these warnings can be safely ignored. All these uses are with arguments provided by the user, when using this as a command line too |
I think you actually want to make the changes in run.ts, and then the build will auto-generate run.js etc. We only want to change .ts files, and we should keep ignoring |
im not sure i understand, the changes i made are in validate.ts and crawl.ts. The reason i checked in built is so that folks can use the code w/o having to download the typescript chain. But if you'd prefer i pull it back out i can |
Ah, do you not need any changes in run.ts? I got confused by the fact that run.js is now being built and checked in. Yeah, I think it would be best to not check in the built JS files. |
Everything else LGTM, just please amend the -o help text to account for this new functionality: https://github.com/brave/pagegraph-crawl/blob/main/src/run.ts#L25 |
15c4403
to
2557de4
Compare
run.js is being checked in bc all the *.js files are checked in, but i didnt make any changes to run.ts. and okie. Just pushed a change that keeps built out |
2557de4
to
cd935a5
Compare
okie pushed an update that also describes the new -o behavior |
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.
Looks great!
cd935a5
to
f71f95a
Compare
f71f95a
to
8196d31
Compare
fixes #66