lz-string icon indicating copy to clipboard operation
lz-string copied to clipboard

Issues and v2 work updates

Open karnthis opened this issue 1 year ago • 9 comments

Work to reduce outstanding issues new and old. Impacted items include:

  • #184
  • #177
  • #110
  • #127

List to be updated as work is completed.

karnthis avatar Jan 17 '24 07:01 karnthis

@Rycochet your thoughts, if you would please.

karnthis avatar Jan 25 '24 02:01 karnthis

Almost there I think :-D

Rycochet avatar Jan 25 '24 09:01 Rycochet

I have everything done except the tests. since you redid the library I am having issues as my tests no longer work but the code being tested did not change. @Rycochet can you go into details on your process for setting up the base64 tests, since that is very similar to what the new tests need?

karnthis avatar Feb 05 '24 23:02 karnthis

@karnthis The biggest thing is that the tests will fail when there is a fix to the underlying code - they're comparing against a "known good" binary output, but in reality the fix means that's not correct any more - you should be able to delete the files for the two fixed encoders, and re-run the test.sh script with the -u option to update those files - which will then be used by the actual vitest tests - do feel free to update things and push with those tests still failing if it's not clear (and then I can checkout locally and give any other pointers that might be needed) :-)

Rycochet avatar Feb 05 '24 23:02 Rycochet

(Note that once this is merged I want to add specific handling for the legacy versions into the test scripts - but not entirely sure what form that needs to take!)

Rycochet avatar Feb 05 '24 23:02 Rycochet

considering the significant number of changes that have happened to the master branch since this started I am considering scrapping what is here and starting fresh. The work still needs to be done but it will need to be approached differently now that things have stabilized a bit.

@Beeloo0011 what?

karnthis avatar May 30 '24 19:05 karnthis

Beeloo0011 what?

@karnthis

I think this is a bot. Their GitHub history is really bizarre. Like they're probing for insecure repos or something.

wkrick avatar May 30 '24 20:05 wkrick

yeah that was my assessment too, was curious to see if I would get a response. didn't expect someone else to reply lol.

karnthis avatar May 30 '24 20:05 karnthis