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.

Sign up for GitHub

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

Jump to bottom

PFM Review / pfm_require and always-nested usage #395

Open
ygini opened this issue Dec 31, 2020 · 0 comments
Open

PFM Review / pfm_require and always-nested usage #395

ygini opened this issue Dec 31, 2020 · 0 comments

Comments

@ygini
Copy link

ygini commented Dec 31, 2020

Currently always-nested is a pfm_require value used only in 5 manfiest, and 3 of those manifest are just variant of the same app.

I recommend replacing all always-nested by always since it does not really seems to have any kind of effective difference with always in the way pfm are wrote.
@ygini ygini changed the title PFM Review / pfm_require and always-nested usage PFM Review / pfm_require and always-nested usage Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ygini