Skip to content

feature: Adds public folder #365

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

Closed
wants to merge 4 commits into from

Conversation

cwramsey
Copy link
Contributor

Re: #322

This adds a Broccoli funnel that will create a public folder in dist that contains only a .gitignore on build.

This is verified with a test added in e2e_workflow.spec.js

@@ -87,10 +87,16 @@ Angular2App.prototype.toTree = function () {
destDir: 'vendor'
});

var publicDirTree = new Funnel(path.join(sourceDir, 'public'), {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually this isn't in sourceDir, it should be on the root itself, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, it was my understanding it would be pulled from src and moved to dist. The issue wasn't very detailed though, so that was my fault for not asking.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to clarify, you'd prefer the public directory to live in the project root, then be moved to dist from there, yes? Or are we skipping all that and just adding the public folder in the root with a .gitignore to force git to recognize it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad, I talked to the current owner of this feature so we knew :)

I would like to move the content of the public folder inside the dist, yes. Not make a dist/public, but rather have public/**/* copied to dist/**/*.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, makes more sense now. But just so I'm clear, where do you want public to live? :) In the root or src?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the root. It's not sources, it's assets :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, that makes more sense now. Appreciate it!

@hansl
Copy link
Contributor

hansl commented Mar 30, 2016

This is looking great!

If you could just squash all your commits into one (if you need help we can help you) and then I'll merge that commit.

Good work 👍

@hansl hansl added pr_action: cleanup feature Issue that requests a new feature labels Mar 30, 2016
@cwramsey cwramsey force-pushed the adding-public-folder branch from f9a6b1d to f4f5464 Compare March 30, 2016 00:42
@cwramsey
Copy link
Contributor Author

Thanks @hansl! I just rebased everything into a single commit for ya.

@hansl
Copy link
Contributor

hansl commented Mar 30, 2016

You should also clear the Merge commit ;)

@cwramsey cwramsey force-pushed the adding-public-folder branch from 7779adc to 396e662 Compare March 30, 2016 00:45
@cwramsey cwramsey force-pushed the adding-public-folder branch from 396e662 to ebe438d Compare March 30, 2016 00:46
@hansl
Copy link
Contributor

hansl commented Mar 30, 2016

@cwramsey Seems like you did something wrong... you'll need to rebase on top of master that's in the original repo (upstream). If you have time I can hop on gitter to help, or if you know what's going on I'll let you fix it :)

I can also just fix it in a separate branch and close this PR. Your name will be on the commit.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@cwramsey
Copy link
Contributor Author

I'm fine with you shoving it into a separate branch. My git skills are lacking after a very short night of sleeping last night. That's what I get for trying out github's new update branch button instead of doing it manually!

@cwramsey cwramsey force-pushed the adding-public-folder branch from 90752c9 to da221b7 Compare March 30, 2016 01:27
@cwramsey cwramsey closed this Mar 30, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants