-
-
Notifications
You must be signed in to change notification settings - Fork 389
Consider restoring the old Eval plugin #1276
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
Comments
👍 for it. Although its custom parser is rewritten carefully in #1232 (not merged though), maintaining its own parser and try not to introduce infinite loops to freeze entire HLS at the same time can be a complicated process. Hopefully, changes in #1232 will stabilise comment parsing of Extended Eval Plugin, I think it is safe to set the default Eval plugin to Extended mode provided that the PR gets merged. |
Ok, #1232 sounds promising, i guess we should make a minor release once it is merged |
yeah, we should release a version with the eval fix but without hiedb, maybe it does not worth |
I want to confirm: not within a few days, but February release willbe made once hiedb change works properly, right? |
@konn Yeah, I believe that's the original intention. |
Closing since nothing has happened and it seems unlikely we're going to do this |
The extended Eval plugin was merged in #438 replacing the original Eval plugin. It is capable and powerful, but also complicated and dangerous - its custom parser has a tendency to error out and bring down the entire process, and the additional features can be hard to understand.
Many users are not aware of the extra features for running doc tests and properties, changing settings and imports, etc. and would be better served by the simpler original Eval plugin, but unfortunately it's now gone.
Proposal: bring back the original Eval plugin under a new name, e.g.
hls-eval-simple
, and ship with both linked and config to select which one gets used, just like we do with formatters.The text was updated successfully, but these errors were encountered: