Feature: Linkwarden service widget

[PyrokineticDarkElf]

Proposed change

Minimal version of #3832

These changes remove everything except the stats fields:

Relevant API responses:

/api/v1/collections:

{
    "response": [
        {
            "id": 8,
            "name": "Homelab",
            "description": "",
            "color": "#ff0000",
            "parentId": null,
            "isPublic": false,
            "ownerId": 1,
            "createdAt": "2024-04-18T21:45:13.843Z",
            "updatedAt": "2024-04-18T21:45:13.843Z",
            "parent": null,
            "members": [],
            "_count": {
                "links": 24
            }
        }
    ]
}

/api/v1/tags:

{
    "response": [
        {
            "id": 118,
            "name": "HTML",
            "ownerId": 1,
            "createdAt": "2024-04-19T09:20:56.287Z",
            "updatedAt": "2024-04-19T09:20:56.287Z",
            "_count": {
                "links": 1
            }
        }
    ]
}

Notes:

I had to disable no-underscore-dangle in ESLint using comments due to API constraints.

/* eslint-disable no-underscore-dangle */
Some code
/* eslint-enable no-underscore-dangle */

Type of change

• New service widget
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation only
• Other (please explain)

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

[shamoon]

Thanks for modifying this PR, ill close the other.

So, my guess is you generated this using AI, so a few things:

1. The code is messy and un-human (consts for things that are used 1 time).
2. The proxy here is completely unnecessary, the screenshot below is with it removed.
3. We ask that people disclose when they do this because of these quality issues.

In general it's ok to use AI as a starting point but it really needs to be managed carefully. Also, I dont mean this disrespectfully at all but it's sort of disappointing when reviewing a PR is actually more work than creating it from scratch. Definitely something to keep in mind if youre planning to open PRs in other projects.

I went ahead and pushed the changes rather than request them all. Thanks for your interest in the project

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.