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

Fix PIO warning about new marlin config #18935

Merged

Conversation

rhapsodyv
Copy link
Member

@rhapsodyv rhapsodyv commented Aug 6, 2020

Description

PIO warns about the new marlin. env config. To get rid of PIO warnings, we need to prefix the new config with custom_.

I really do like marlin.. But with custom_marlin. we get no warning.

Verified in the PIO source code: ~/.platformio/penv/python-xx/site-packages/platformio/project/config.py:170

Benefits

Fixes #18934

Related Issues

#18934
#18919

@thinkyhead
Copy link
Member

Aha, I figured there must me some facility in PlatformIO to allow for custom but ignored values.

This will work. I was thinking maybe custom_ alone would be fine, but custom_marlin. leaves open the creation of custom_other.SOMETHING if needed … and we get to keep the dot.

@thinkyhead thinkyhead merged commit c3fdc7f into MarlinFirmware:bugfix-2.0.x Aug 6, 2020
Speaka pushed a commit to Speaka/Marlin that referenced this pull request Aug 13, 2020
albertogg pushed a commit to albertogg/Marlin that referenced this pull request Aug 31, 2020
@rhapsodyv rhapsodyv deleted the fix-pio-config-warning branch October 25, 2020 00:17
vgadreau pushed a commit to vgadreau/Marlin that referenced this pull request Dec 9, 2020
ahmetcemturan pushed a commit to ahmetcemturan/Marlin that referenced this pull request Jan 21, 2021
ahmetcemturan added a commit to ahmetcemturan/Marlin that referenced this pull request Jan 23, 2021
kageurufu pushed a commit to CR30-Users/Marlin-CR30 that referenced this pull request Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants