@ProCode2 can you handle this issue (https://github.com/coronasafe/care_fe/pull/7000#issuecomment-1895353628) also in this pr. To replicate the issue, In the front end, 1. Go to a patient consultation dashboard 2. Link an Abha number 3. Go to another patient's consultation dashboard 4. Link the same Abha number again That will trigger the error you see in the comment mentioned. Have a conditional check if the Abha number already exists before creating the Abha number, and return a response with a neat error message.

https://github.com/coronasafe/care/pull/1821#issuecomment-1895370324

> @khavinshankar  @nihal467 this is an existing issue, will create a new issue to handle this (it is a backend issue). It is caused because of trying to link the same Abha number multiple times

https://github.com/coronasafe/care_fe/pull/7000#issuecomment-1895353628

Yes, that works, while logging, just use the function name or the endpoint, that should be enough.

https://github.com/coronasafe/care/issues/1815#issuecomment-1888374736

Test fails not related to the changes in this pr

https://github.com/coronasafe/care/pull/1807#issuecomment-1877037300

@rithviknishad Currently, there is no way to identify the issue number if the issue is linked (connected) using UI, so lets handle that part while moving to Graphql. This is the event created for connection using UI <img width="872" alt="image" src="https://github.com/coronasafe/leaderboard/assets/29787772/31120282-445b-4e9e-9a38-a375c13b9ec6"> If we want to do this now using rest API, we need to iterate through all the open issues and get the cross-referenced event which seems unnecessarily expensive. PS: This is an issue only when the issue is connected with PR in PR's UI and not vice versa.

https://github.com/coronasafe/leaderboard/pull/167#issuecomment-1853285978

Closed this pr in favour of #155

https://github.com/coronasafe/leaderboard/pull/155#issuecomment-1853270414

@rithviknishad can u assign this to me

https://github.com/coronasafe/leaderboard/issues/153#issuecomment-1849392026

@rithviknishad can u assign this to me

https://github.com/coronasafe/leaderboard/issues/143#issuecomment-1849391843

Yes, that makes sense, then maybe we could just store the number of lines changed for each merged prs, something like ```js { lines: { added: number; removed: number; modified: number; } } ```

https://github.com/coronasafe/leaderboard/issues/144#issuecomment-1848978960

@rithviknishad I think we can accomplish this using `https://api.github.com/repos/{owner}/{repo}/compare/{base}...{head}` API I just wanted to know the use case. Wouldn't adding the file changes to JSON make them heavy over time?

https://github.com/coronasafe/leaderboard/issues/144#issuecomment-1848975903

@Pranshu1902 can you resolve the merge conflicts and wire up the respective backend for this, so that @nihal467 can test it

https://github.com/coronasafe/care_fe/pull/6223#issuecomment-1845249870

Fixed in #117

https://github.com/coronasafe/teleicu_middleware/issues/116#issuecomment-1836335401

When the asset was deleted and recreated, the asset uptime started working correctly. Closing this issue as done, incase if this issue persists, feel free to reopen this issue or create a new issue. cc: @nihal467

https://github.com/coronasafe/care_fe/issues/6524#issuecomment-1833848334

> @khavinshankar maybe we can just merge off the configurations for now, and we can eventually migrate existing files as we go? It won't cause functionality issues right other than eslint errors. I agree

https://github.com/coronasafe/care_fe/pull/6557#issuecomment-1831733923

@thedevildude fix the merge conflicts

https://github.com/coronasafe/care_fe/pull/6596#issuecomment-1831215618

Will merge it on Dec 15th (when the feature is no longer supported) cc: @rithviknishad @nihal467

https://github.com/coronasafe/care_fe/pull/6725#issuecomment-1827992492