[Feature] Upgrade project's JavaScript code with the power of ES6! for better performance.

[Keerthivardhan1]

Problem

Using these concepts can lead to more concise and readable code, with fewer bugs and better performance. Additionally, many of these concepts are supported by modern browsers and Node.js versions, making it easier to write code that can be run in multiple environments.

Description

There are several ways to improve the implementation, such as replacing all instances of var with const or let, implementing arrow functions, and ensuring that each function handles edge cases.

For eg:-

The function "getUrlVars()" declared in the "listing.html" file uses the "var" keyword for variable declaration, which may lead to variable scoping issues. Additionally, the code doesn't account for URL encoding of parameter values, which may cause incorrect capture of special characters. Moreover, the variable names used in the function are not very descriptive, which could make the code harder to comprehend and update.

Implementation

• I would be interested in implementing this feature.

[Keerthivardhan1]

we welcome and encourage anyone who is interested to contribute their insights and suggestions to this issue. Your input is highly valued and appreciated.

[justaskulkarni]

This issue is similar to:

• Improve the JavaScript syntax in the listing.html page  #17

[possumbilities]

This is similar to #17, but not quite a duplicate so I'm leaving it open.

[Keerthivardhan1]

Thank you @possumbilities ,
Based on my understanding I have optimized the JavaScript code .
This is the PR : - #167
Thanks a lot for letting me to work on this issue.

[Murdock9803]

@possumbilities I can see an unmerged PR for this issue. Can I work on this issue from the starting or It is solved ?

[possumbilities]

@Murdock9803 Hi! something that could be helpful is testing the existing PR and commenting if you find any errors/if you don't. I think that's been the hold on that PR is it needed more thorough testing, and hasn't yet gotten it to a degree to fully be approved.

[Murdock9803]

@possumbilities
The PR looks fine and doesn't contain any errors, but it surely has merge conflicts due to merging of other commits after the PR got opened. Also, as PR #151 is merged, some functions got removed from the codebase. So it would be better if @Keerthivardhan1 resolves the merge conflicts by syncing the code. I can help with that too