@AntonioMrtz Could you please review my pull request and merge it? I'm a beginner and have done my best to deliver.

Thank you!

Hi @yashwanthvarma18 , thanks for your work, I will try to review it ASAP :) . We have a list of contributors in Readme.md and Contributors.md, feel free to add yourself keeping the format and commit the changes :)

I runned the pipelines, it seems like eslint, prettier and some tests are failing. Can you take a look at it? Let me know if you need any help

@AntonioMrtz
I am not familiar with what these issues means and caused due to
Please let me know how to resolve them
ESlint Check / run-frontend-lint (pull_request)
Frontend Style Prettier / run-frontend-style-check (pull_request)
Frontend Tests / frontend-test (pull_request)

@AntonioMrtz I am not familiar with what these issues means and caused due to Please let me know how to resolve them ESlint Check / run-frontend-lint (pull_request) Frontend Style Prettier / run-frontend-style-check (pull_request) Frontend Tests / frontend-test (pull_request)

If you go inside details for each failed pipeline you can see the error logs. To reproduce it locally run the follow commands:

• Prettier: npm run format:write. Pipeline checks styling is correct
• Lint: npm run lint. Check linting rules
• Tests: npm run tests. Tests are failing because of the modifications

@AntonioMrtz
I finally made it! All tests are running without any issues. You can check it out too. It took me four hours to figure out where I made mistakes in the implementation, but I learned a lot from them. Thank you for giving me this opportunity!

@AntonioMrtz what can i do to correct this
Check OpenAPI schema is updated / check-openapi-schema-is-updated (pull_request) Failing after 1m

@AntonioMrtz Please check the new commit and let me know if there is any issue again

Hi @yashwanthvarma18 , just a few things:

I know it probably took some time to do the adjustments but we don't want all the external .erb packages, markdown doc files and more to use frontend prettier format. Also I found that many rules that we don't use are being applied. I'm confident to say that this can be due to running npm run commands in an incorrect directory or that these commands didn't follow the ruleset they have as input

As you can see here, the custom commands that run with npm run have parameters that affect the output such as file to be ignored and the rules to be applied.

"scripts": {
    "lint": "cross-env NODE_ENV=development eslint src/ --ext .js,.jsx,.ts,.tsx --fix",
    "format:write": "prettier src/ --write --ignore-path .prettierignore",
}

Example with npm run format:write: only src/ files will be formatted and it will honor .prettierignore rules

What would I do:

• Revert back to commit 89e47c85b53a5e12749f56045ef3ed5b5e520b62
• Run the the commands I mentioned in previous message while being in the directory Electron/ and making sure the command rules are being honored
• Make the adjustments that the commands output, there won't be a lot, it will only output warnings about code that YOU changed, the actual codebase passes the pipelines with no adjusments
• I will review the provided code :)

Let me know if you have any question, code looked good but I cannot merge a lot of modified files that were out of scope for this task :)

@AntonioMrtz
I spent most of the day working on this, and I understand that you're not satisfied with the PR. That's fine—I hope the code I pushed can still be helpful to you in some way. Thanks for the opportunity!

@AntonioMrtz I spent most of the day working on this, and I understand that you're not satisfied with the PR. That's fine—I hope the code I pushed can still be helpful to you in some way. Thanks for the opportunity!

Yeah, I checked the changes and know they have took a long time to implement. I feel bad for it :( , but we have to keep the codebase with the same style and format