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

Freaking out YML parser is unhandled #78

Open
4 tasks done
prplwtf opened this issue Jan 9, 2025 · 0 comments
Open
4 tasks done

Freaking out YML parser is unhandled #78

prplwtf opened this issue Jan 9, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@prplwtf
Copy link
Member

prplwtf commented Jan 9, 2025

Current Behavior

When messing up quotes in a extension configuration file, Blueprint will not handle it as an error but will also incorrectly install an extension.

Expected Behavior

Blueprint or the YML parser it uses to throw a user-readable error and stop the extension transaction.

Steps to Reproduce

Mess up quotes in any Blueprint extension configuration file. This includes conf.yml, Components.yml and Console.yml.

option: item""

Blueprint Version

beta-2025-01

Panel Version

1.11.10

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details and tested my reproduction steps.
  • I have checked to my best capabilities and believe this is a bug with the software, and not a configuration issue with my specific system.
  • I have made sure to check that this bug is the fault of Blueprint and is not caused by stock Pterodactyl.
@prplwtf prplwtf added the bug Something isn't working label Jan 9, 2025
@prplwtf prplwtf changed the title Freaking out YML parser causes strange issues. Freaking out YML parser is unhandled Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant