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

Skript Parsing output format (messy) #3505

Closed
AyhamAl-Ali opened this issue Oct 30, 2020 · 4 comments
Closed

Skript Parsing output format (messy) #3505

AyhamAl-Ali opened this issue Oct 30, 2020 · 4 comments
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).

Comments

@AyhamAl-Ali
Copy link
Member

AyhamAl-Ali commented Oct 30, 2020

I have been using SkriptEnhanced script made by Duetro and it was amazing how it formats the script parsing/reloading output in a very clean and readable way, also I can autocomplete script names, and it shows more details about errors and the line that has the error etc.

This script doesn't work anymore because it needs mundoSk for json stuff and mundoSk is deprecated, so I am back to Skript's default parsing output.

I would love to see Skript itself enhance that thing and make it a vanilla thing and and I'm sure many others would love that too.

What to enhance?

  • Add empty lines between every line (make it easier to read)
  • Make Error %line% more visible (use it on its own line and use colors)
  • Optional: Add hover event over every error showing the error line and some other surrounding lines
  • Reloading time

Images (from SkriptEnhanced):

image
image
image

image

@ShaneBeee ShaneBeee added enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements). labels Oct 30, 2020
@ShaneBeee
Copy link
Contributor

This is definitely a neat idea, and would help out with errors for sure.

@Misio12320
Copy link

Well, it looks good but what if people like old one? Might add into config file the old and new parser output?

@Pikachu920
Copy link
Member

Pikachu920 commented Nov 1, 2020

what does the old one provide that the new one doesn't? if they both provide the same info, i don't really see a reason keep the legacy one in.

@Misio12320
Copy link

The old one provide red color errors. Skript = coding. Dev-C++ contains too the red color when error occur. Maybe some older users of Skript like the old one atmosferic and would like to return to it when the new one release, dont they?

@TPGamesNL TPGamesNL added the PR available Issues which have a yet-to-be merged PR resolving it label Apr 25, 2021
@TPGamesNL TPGamesNL added completed The issue has been fully resolved and the change will be in the next Skript update. and removed PR available Issues which have a yet-to-be merged PR resolving it labels Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed The issue has been fully resolved and the change will be in the next Skript update. enhancement Feature request, an issue about something that could be improved, or a PR improving something. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
Projects
None yet
Development

No branches or pull requests

6 participants