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

Use one settings object per processor #23

Closed
wooorm opened this issue Feb 11, 2017 · 0 comments
Closed

Use one settings object per processor #23

wooorm opened this issue Feb 11, 2017 · 0 comments
Labels
🗄 area/interface This affects the public interface 💪 phase/solved Post is done 🧑 semver/major This is a change 🦋 type/enhancement This is great to have

Comments

@wooorm
Copy link
Member

wooorm commented Feb 11, 2017 

proc.data('settings', {a: true, b: false})

Then, presets with settings (GH-22) can extend that object.

Additionally, options should be removed from parse / stringify / process / pipe.
@wooorm wooorm mentioned this issue Feb 11, 2017
Closed
@wooorm wooorm mentioned this issue Feb 20, 2017
Merged
11 tasks
@wooorm wooorm closed this as completed in 0db0928 Feb 23, 2017
@wooorm wooorm added ⛵️ status/released 🗄 area/interface This affects the public interface 🦋 type/enhancement This is great to have 🧑 semver/major This is a change labels Aug 10, 2019
@wooorm wooorm added the 💪 phase/solved Post is done label May 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🗄 area/interface This affects the public interface 💪 phase/solved Post is done 🧑 semver/major This is a change 🦋 type/enhancement This is great to have
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wooorm