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

Support preserving folder structure (recursive) #61

Closed
sindresorhus opened this issue Jun 11, 2019 · 5 comments · Fixed by #77
Closed

Support preserving folder structure (recursive) #61

sindresorhus opened this issue Jun 11, 2019 · 5 comments · Fixed by #77
Labels
enhancement 🎁 Rewarded on Issuehunt This issue has been rewarded on Issuehunt help wanted

Comments

@sindresorhus
Copy link
Owner

sindresorhus commented Jun 11, 2019

Issuehunt badges

This would fix: #30, #10, #40, #60
(If you want to take on this issue, ensure you read those issue threads too, for context)

And see #32 for a previous attempt.

This tasks also includes adding support for it in https://github.com/sindresorhus/cpy-cli.

This tasks also requires you to write a lot of tests.

And some inspiration from other tools:

Question: Should it be recursive by default? Why? Why not? Include reasoning.


Note: This is not an easy issue. It requires you to have good JavaScript and Node.js experience. I expect you to do a good job. Instead of asking to many questions, present solutions. The point of a issue bounty is to give me less work, not more. 🙌


IssueHunt Summary

idered idered has been rewarded.

Backers (Total: $120.00)

Submitted pull Requests


Tips

@sindresorhus sindresorhus mentioned this issue Jun 11, 2019
4 tasks
@issuehunt-oss issuehunt-oss bot added the 💵 Funded on Issuehunt This issue has been funded on Issuehunt label Jun 11, 2019
@IssueHuntBot
Copy link

@issuehunt has funded $120.00 to this issue.


@friendlyanon
Copy link

Hello, I'm interested in solving this issue for you, however I would like to inquire about some details to clear a few things up for me.
What would this recursive option do differently than the parent: true option? Omit the leading segments in the destination path? (Is that what #40 is about?)
As far as I can tell doing cpy("b", "a", { parents: true }) on b/c/d.js will result in a/b/c/d.js, since globby does a recursive listing already.
What is a clear example where cpy currently doesn't behave as expected and what would the expected outcome be?
Thank you for your time.

@sindresorhus
Copy link
Owner Author

The reason there's a fairly large bounty on this issue is that I don't have all the answers. It's up to the submitter to come up with a good solution. Many of the deficiencies of the current behavior is documented in the linked issues.

@chrispcode
Copy link

Just an opinion, I think what people are looking for is reproducing this behavior:
image

In this kind of API:
image

Or something similar...

Repository owner deleted a comment from janat08 Sep 29, 2020
Repository owner deleted a comment from janat08 Sep 29, 2020
Repository owner deleted a comment from papb Sep 29, 2020
@issuehunt-oss
Copy link

issuehunt-oss bot commented Jul 12, 2021

@sindresorhus has rewarded $108.00 to @idered. See it on IssueHunt

  • 💰 Total deposit: $120.00
  • 🎉 Repository reward(0%): $0.00
  • 🔧 Service fee(10%): $12.00

@issuehunt-oss issuehunt-oss bot added 🎁 Rewarded on Issuehunt This issue has been rewarded on Issuehunt and removed 💵 Funded on Issuehunt This issue has been funded on Issuehunt labels Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🎁 Rewarded on Issuehunt This issue has been rewarded on Issuehunt help wanted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants