Add article link to the README

[kamranbekirovyz]

Hi @nohli. Thanks for giving the chance to add my article to the README as a reference.

Please, look at the changes I've made. I did my best, but, let me know if we can improve the sentence.

[nohli]

Cool, great job! Thank you for your contribution.

Here are a few suggestions to improve the code and documentation:

1. Using haptic feedback instead of haptic feedbacks is more accurate. As well in this PR, as in the article. What do you think?

2. In the article, await is missing before a few method calls.

3. Consider changing the check from:

    if (_canVibrate ==true) {

to

    if (_canVibrate ?? false) {

4. To prevent instantiation of the class and avoid suggestions from the code editor, add a private constructor:

HapticsHelper._();

Thanks again for your work on this. These changes can enhance the accuracy and robustness of the code.

[kamranbekirovyz]

@nohli thanks, I'll update the article with the suggestions of yours and let you know.

[nohli]

Thanks for updating.

Have you looked at points 1-3 from my previous comment?

[kamranbekirovyz]

Thanks for updating.

Have you looked at points 1-3 from my previous comment?

Yes. The first one is done, I even changed the title of the article. About the 3rd point, if you think it is very crucial I can update it right now.

[nohli]

Regarding the article:

1. I still notice numerous instances of haptic feedbacks.
2. Additionally, there are still missing awaits before method calls.
3. was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

[kamranbekirovyz]

Regarding the article:

1. I still notice numerous instances of haptic feedbacks.
2. Additionally, there are still missing awaits before method calls.
3. was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

[nohli]

Regarding the article:

1. I still notice numerous instances of haptic feedbacks.

2. Additionally, there are still missing awaits before method calls.

3. was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

Great, thanks for updating! 🙏🏽

I will merge asap.

There is still one instance of "haptic feedbacks", would be good to change it to "haptic feedback".

Explanation:
The term “haptic feedback” is typically used in the singular form, much like the words “information” or “data.” All these terms are collective nouns, meaning they refer to a concept that inherently includes multiple instances.

[kamranbekirovyz]

Regarding the article:

1. I still notice numerous instances of haptic feedbacks.

2. Additionally, there are still missing awaits before method calls.

3. was referring to the no_literal_bool_comparisons linter rule: https://dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: https://dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

Great, thanks for updating! 🙏🏽

I will merge asap.

There is still one instance of "haptic feedbacks", would be good to change it to "haptic feedback".

Explanation: The term “haptic feedback” is typically used in the singular form, much like the words “information” or “data.” All these terms are collective nouns, meaning they refer to a concept that inherently includes multiple instances.

My pleasure.

Although, I think it should be "a set of haptic feedbacks" you and ChatGPT are in majority. So, changed that too.

[nohli]

Regarding the article:

1. I still notice numerous instances of haptic feedbacks.

2. Additionally, there are still missing awaits before method calls.

3. was referring to the no_literal_bool_comparisons linter rule: dart.dev/tools/linter-rules/no_literal_bool_comparisons (Effective Dart: dart.dev/effective-dart/usage#dont-use-true-or-false-in-equality-operations)

In my opinion, an article explaining code should be precise.

Updated the article again. Is there anything missing again?

Great, thanks for updating! 🙏🏽
I will merge asap.
There is still one instance of "haptic feedbacks", would be good to change it to "haptic feedback".
Explanation: The term “haptic feedback” is typically used in the singular form, much like the words “information” or “data.” All these terms are collective nouns, meaning they refer to a concept that inherently includes multiple instances.

My pleasure.

Although, I think it should be "a set of haptic feedbacks" you and ChatGPT are in majority. So, changed that too.

hahaha

Actually the first thing was I googled the plural version and didn't find results, only singular.

[nohli]

Thank you so much!

[kamranbekirovyz]

@nohli my pleasure to be featured on the README with my new Flutter blog. Thanks for the opportunity and, especially, your time.

[nohli]

I hope you have fun and success with your blog! 🤝🏽