Skip to content

Conversation

@vixalien
Copy link
Owner

Hello everyone, I'm launching Project Clarity, which will be a major rewrite of the application and will probably lead to our first v1 (#2).

There's a couple of reasons, and I'll list a few starting from the most heavy ones:

  1. The current way we parse content was inspired by https://github.com/sigma67/ytmusicapi and relies heavily on guesswork. We parse blindly, expecting JSON to have a certain structure, and in the case of errors, we throw a weird error that usually only myself can decode. The new version of muse will "know" about the structure of the various data types provided by YouTube music's API and will parse them accordingly.
  2. The current source has no tests :/
  3. The current version has poor documentation, and users sometimes get confused.
  4. The current version has many exported symbols, which makes the library users confused.
  5. You can find the same parsers implemented many times elsewhere
  6. The nav.ts file is getting too huge imo, and is almost incomprehensible

@vixalien vixalien changed the title Project Clarity: Parsing overhaul Project Clarity: Parsing Rewrite Aug 30, 2024
@vixalien vixalien force-pushed the wip/vixalien/parsing branch from 199aac3 to aa2d4b8 Compare November 2, 2024 11:51
@afkcodes
Copy link

waititng for this to release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants