Skip to content
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

Idea for local override #87

Open
metakeule opened this issue Apr 30, 2020 · 2 comments
Open

Idea for local override #87

metakeule opened this issue Apr 30, 2020 · 2 comments

Comments

@metakeule
Copy link

Local Override: Stable allows local bundles that are just [relative] path entries in the bundle, resulting in canonicalized paths in the PONYPATH. How can we do this while also tracking a remote location to allow local development of a published library? That is: use remote, fork remote and work on local, commit fork to remote and go back to using that. This could be a simple matter of tracking the local location as a temporary override. Or, we just let the developer update (remove+add) the bundle with the alternate locator. Or, use a more general alias technique like go mod?

My idea: Use a general alias technique in a separate file (e.g. local-overrides.json). This way the developer(s) could have this file but do not check it into the repo. So the users cloning the repo won't have the overrides (but could add them easily if needed).

@SeanTAllen
Copy link
Member

@metakeule what is the quoted text from?

@metakeule
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants