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

Script does not read "RequirementsTemplateAppName" from preferences #1

Closed
AK-Zephyr opened this issue Aug 14, 2018 · 2 comments
Closed
Assignees

Comments

@AK-Zephyr
Copy link

The script will throw errors messages when trying to apply rules to an application if you use any name other than "Application Requirements Template". The issues is due to the script not importing the name of the "RequirementsTemplateAppName". It currently uses a hard coded string.

The auto generated template is called "Application Requirements Template 1" causing rules to fail for most users.

Line 37 needs to be changed to:
$Global:RequirementsTemplateAppName = $PackagerPrefs.PackagerPrefs.RequirementsTemplateAppName

@asjimene asjimene self-assigned this Aug 14, 2018
@asjimene
Copy link
Owner

This has been fixed. Thank you for the feedback 😄

asjimene added a commit that referenced this issue Aug 14, 2018
Added fix for: Issue #1
@AK-Zephyr
Copy link
Author

Thanks! This script is great. Thank you for sharing it.

I'll contribute what I can as I get it working in my environment.

asjimene pushed a commit that referenced this issue Sep 24, 2019
asjimene pushed a commit that referenced this issue Feb 5, 2020
Merge pull request #27 from ianperrin/master
asjimene pushed a commit that referenced this issue Jul 7, 2022
add options for alternate perference and recipe path
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