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
Rule: no-forward
#69
Comments
Should rule recommend to use "greedy" version of If we could somehow define specific situations when it does matter, then rule could provide better hint on which kind of sample to use 🤔 |
In my opinion, differences in priority isn't important in 99% cases. I think, if you rely on them, you know it. |
I agree, but i think, that this rule can backfire, if this plugin is added to a project, that was developed for some time without it and there is a case when priority matters It can go like this: user will change I think, hint of the rule should at least mention that there is a such possibility |
Good point |
After all, if there's a really-really important case where you should use |
So, I've decided to add this rule to plugin, but do not include it to recommended preset because it can affect program results. |
I'd like to ban
forward({ from, to })
operator, and replace it withsample({ clock, target })
insteadThe reason is that
sample
does the same thing thatforward
does, but it's completely superior in terms of featuresI figured out that every time I write
forward
somewhere, after a ~hour I rewrite it tosample
because OK now I need to transform my dataThe only problem is that forward has different execution priority rather than sample, so sometimes it might be important
The text was updated successfully, but these errors were encountered: