-
Notifications
You must be signed in to change notification settings - Fork 49
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
Feature request: Use newer expressions #36
Comments
Hi Josh, great, that sounds very promising for multiple new cleanup rules! We'd have to check about limitations for automation in the individual cases, of course, but looking forward to this! Kind regards, |
Hi Josh, just to keep you updated, I now implemented an important prerequisite to some of these ideas, namely
This is needed, obviously, because these newer expressions don't change the system fields, and we must excluded unexpected cases from cleanup (e.g. when the system field is first stored in a variable and evaluated at a different point). To be continued! Kind regards, P.S.: Points 6 and 7 are already implemented with the "Replace TRANSLATE with string functions" rule, but |
Hi Josh, FYI, for point 10 "String templates", a dedicated issue #116 was opened, so discussion for this particular point could be continued there. Kind regards, |
Hi @jmgrassau, just circling back to this one. The tool has become very stable and useful! Do you think any of these would make it as a priority soon? |
Hi Josh, thanks for the reminder, and really sorry that (due to limited capacity) there was no progress here for such a long time! Hm, if you could choose, which of those 10 open ideas would you find most useful to start with? Kind regards, |
I think I’ll also try to re-order the rest based on priority, and others can give their input here as well. |
Great! Looks good, and you are right there are some outliers to be aware of. |
Hi Josh, release 1.14.0 will also offer the new rule "Replace READ TABLE with table expression" (for 3. line_exists( ) and 10. line_index( ), and additionally for ASSIGN): Examples: However, unfortunately, the rule can't automate everything, which is also explained in the examples: Kind regards, P.S.: Is 6. translate( ) fulfilled with the rule "Replace TRANSLATE with string functions" or is anything missing there? |
These are great additions, thank you! Also, yes |
Hi Josh, perfect, thanks once again for this inspiring list! (And nicely done with the ticks, references and version numbers!) Already doing some research on some of the other points … Kind regards, |
There's a dedicated issue for |
Hi Josh, version 1.15.0, which was just released, now includes the new cleanup rules "Use string templates to assemble text" (for 2.) and "Replace CONDENSE with string function" (for 5.)! Kind regards, |
There are a number of newer expressions that seem like a good fit for a rule to replace the old syntax, such as:
partially complete in 1.15.0
refer to Automated Conversion from Old String Concatenations to String Templates #116
1.14.0
1.14.0
1.15.0
1.0.0
1.0.0
1.14.0
The text was updated successfully, but these errors were encountered: