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

feat(url_resolver): Allow a developer to customize their package prefix #3794

Closed
wants to merge 1 commit into from

Conversation

TedSander
Copy link
Contributor

Allow a developer to specify a package prefix where the 'package:' dart urls
will be resolved. By default this will be '/packages' keeping the current
behavior, but allows for flexibility of different environments where a
developer may not control their directory structure.

@TedSander TedSander added the action: review The PR is still awaiting reviews from at least one requested reviewer label Aug 22, 2015
@mhevery mhevery added pr_state: LGTM action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Aug 24, 2015
@mary-poppins
Copy link

Merging PR #3794 on behalf of @mhevery to branch presubmit-mhevery-pr-3794.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Aug 24, 2015
@mhevery mhevery assigned TedSander and unassigned yjbanov Aug 24, 2015
Allow a developer to specify a package prefix where the 'package:' dart urls
will be resolved. By default this will be '/packages' keeping the current
behavior, but allows for flexibility of different environments where a
developer may not control their directory structure.
@TedSander TedSander added the action: merge The PR is ready for merge by the caretaker label Aug 24, 2015
@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Aug 24, 2015
@mary-poppins
Copy link

User @TedSander does not have PR merging privileges.

@TedSander
Copy link
Contributor Author

@mhevery The merge didn't seem successful on this PR. I rebased the CL and reran the travis checks and they seem to be fine. Can you re-run it through the merge queue? I don't have approval for that.

@mhevery mhevery added the action: merge The PR is ready for merge by the caretaker label Aug 25, 2015
@mary-poppins
Copy link

Merging PR #3794 on behalf of @mhevery to branch presubmit-mhevery-pr-3794.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Aug 25, 2015
@TedSander TedSander closed this in 9cc1cd2 Aug 25, 2015
@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants