Find media in Atom/RSS/JSON

[GreenTeaCake]

Fixes #60

Changes (please see the list of commits to get details in organized manner):

• Add new unit tests
• Minor refactoring of existing unit tests

Motivation

Checklist

• [x] Don’t rush. Check all changes in PR again.
• [x] Think about changing documentation.
  • If you added a script to scripts/, add a comment with a description.
  • If you added a new folder, add its description to the project’s README.md.
  • If you added config, describe how we use this tool in the config’s comment.
  • If you added something to the project’s architecture, describe it in the project’s README.md.
  • Try to focus on “why?”, not “how?”.
• [x] If you added a new dependency, check our requirements.
• [x] Think about testing
  • If you added a feature, add unit tests.
  • If you added a new state to the UI, add visual tests.
  • If you fixed the bug, think about preventing bug regression in the future.
• If you changed web client:
  • [x] Think about moving code to core/. What code will also be useful on other platforms?
  • [x] Run pnpm size and check the difference in the JS bundle size. Is it relevant to the changes? Change the limit in web/.size-limit.json if necessary.
  • [x] Think about keyboard UX. Is it easy to use the new feature with only one hand on a keyboard? Is it easy to understand what keys to press?
  • [x] Think about HTML semantics.
  • [x] Think about accessibility. Check a11y recommendations. Think about how screen reader users will use the tool. Is it easy to use on a screen with bad contrast?
  • [x] Think about translations. Will
  • [x] Think about right-to-left languages. What parts of the screen should be mirrored for Arabic or Hebrew languages?
• If you changed the colors token in the web client:
  • [x] Think about app loading styles inlined in index.html.
• If you changed core/:
  • [x] Think about making types more precise. Can you better explain data relations by type?
  • [x] Think about conflict resolution. We don’t need some very smart changing merging; just 2 changes of the same item on different clients should not break the database. What if the user changes an item on one machine and removes it on another?
  • [x] Think about log and storage migration.
• If you changed English translations:
  • [x] Change translation ID if you change the meaning of the text.

[ai]

Ping me when PR will be finished

[ai]

Hi. Do you plan to continue development? If you don’t have enough time, we can make task as free (but you can still continue if you will find a time).

[GreenTeaCake]

Hi. Do you plan to continue development? If you don’t have enough time, we can make task as free (but you can still continue if you will find a time).

Hello! I'm really sorry for the delay. Will try to bring the code for review or ask to un-assign tonight.

[ai]

Sorry, another loader changes. Can you add the media search to core/loader/json-feed.ts too?

The last one, I promise :).

[ai]

Everything else looks good. Great work.

[ai]

Just fix ESLint warnings by running pnpm eslint --fix .

[GreenTeaCake]

Sorry, another loader changes. Can you add the media search to core/loader/json-feed.ts too?

The last one, I promise :).

Sure thing. NP. Will add parsing tonight

[ai]

Thanks! Amazing work.