Closed liorbentov closed 4 years ago
A description would have also sufficed. Creating an issue for errors may be a good idea, but creating issues for increasing readability might be a bit much.
Please update #49 accordingly. I wasn't thinking as well.
This PR solves what run error exactly? Is it the ConnectionAbortedError? Please add a description about what exactly this change solves.
If it's a small issue (ex. readabilty), then only description may suffice. However, if it's a major issue creating an Issue would help document what changed and why.
Sorry for that, it has been a long time since I've posted a PR... When entering the About page, there is a console error that is caused by focusMe implementation.
You meant the browser console? That took me a while to figure out.
While it does get rid of the TypeError, a ReferenceError comes up in the Homepage when one searches for tutorials.
EDIT: Do update custom.js to match with master, there's a conflict.
@Animesh-Ghosh, fixed
Fixing TypeError introduces a ReferenceError.
Where? What are the steps to reproduce?
Sorry, it seems removing the TypeError doesn't introduce the ReferenceError, it already was there before.
Steps to reproduce:
@Animesh-Ghosh , I think it's right to open an issue/bug for that if it's not related. What do you say?
Really need to update the CONTRIBUTING.md
file. 😅
Really need to update the
CONTRIBUTING.md
file. 😅
I don't think that's related as well 🤷♀ What do you want this file to say? Does this PR resolve the error? Does it create a new one? If it resolves the error and doesn't create a new one, I think it's right to merge it and stop the discussion, or at least move it to somewhere proper.
@Animesh-Ghosh , I've opened a PR (#54 ) for fixing the reference error.
@liorbentov should i merge this one or #54 ?
First this one, and then I will update #54
Please create an issue first before creating a Pull Request.
It helps in associating PRs with the issues that they are solving.