feat: support local file paths in addition to remote URLs#23
feat: support local file paths in addition to remote URLs#23fanyang89 wants to merge 1 commit intovet-run:mainfrom
Conversation
Allows vet to process local script files directly without downloading, making it more convenient for local development and testing.
|
Thanks for this! The idea looks good — I'll take a proper look soon. |
|
The main piece we still need to solve is the caching/diffing feature. Applying the current URL-based logic to local file paths will lead to some confusing behavior, since relative paths may vary for the same file (symlinks is an example of another edge case). I see two main options:
What's your gut feeling on which path is better? |
|
Hi @lykhvar, what are your thoughts on this approach? My idea is to treat file paths as just another form of URL, so we can integrate them into our existing URL caching logic. For file renames or path updates, it would be similar to a broken URL. Since we can't track file system changes, we'd simply invalidate the cache for that path. Does that sound reasonable? |
Allows vet to process local script files directly without downloading, making it more convenient for local development and testing.