3.0 migration, docs questions

[MrAwesome]

@DanielleMiu - I'd love to help you out getting 3.0 out the door, have a few questions for whenever you have the time and energy:

1. You mentioned that there are some 2.6 changes that need to be ported to 3.0, do you have a list of those handy?
2. Are there any other changes or code migrations that need to happen before 3.0 is ready?
3. Are there any documentation changes that need to happen other than the README changes already there?
4. Does anything need to change about the deploy process for 3.0? (Also, if you have a sec to write it up I'd love to know what the process is, never done anything with browser extensions until now)

[kheina]

1. pretty much everything in the 0.2.6 llb/diff. iirc @jaredkotoff made the ts branch from 0.2.5 and I meant to update it myself and get the hang of ts at the same time but it just never happened
2. I don't believe so, outside your changes the other day
3. I'm not sure actually. I haven't had the chance to look through the ts code with as much detail as I would like yet. I know it works and when I gave it the once-over it looked good but that's really all I've done
4. @jaredkotoff is probably the better person to ask about the ts procedure. all I do now is run the make chrome and make firefox commands in the make file, check to make sure they're working, and then upload them to the chrome website and firefox addons. knowing vite, it might need to go through npm run build, but I think he actually got that wrapped into the makefile too. at some point I'd like to make a github action to do the make/upload part automatically but it's probably best to wait until firefox can be updated to manifest v3 so it's not building it twice

[jaredcat]

@MrAwesome @DanielleMiu I rebased v0.3.0 off of main: #126
If this looks good, I think we can probably swap current llb-v0.3.0 branch for this one?

[kheina]

yeah, probably. in the end it doesn't really matter, we'll just close whichever pr doesn't get merged. I'm gonna look more at it today and do more testing on your branch

[MrAwesome]

For 0.3.0, is there anything I can help with, or will I just need to wait for #126?

[kheina]

testing and bug fixing and making sure all changes from 0.2.6 are in. I was looking at code earlier and saw it's still using xhr rather than the new fetch logic

[jaredcat]

Yea my rebase needs to be cleaned up. I was going to do it once I got sometime back from vacation. But extra eyes on it either way would be good. Notes on the PR would be helpful

[kheina]

I might want it updated to use tabs since I think it's currently using spaces, but that's all I see taking a quick second look

[kheina]

working on this lately, also adding that verification db. I'm using the checklist I posted in the rebase branch as my guide

[kheina]

#143 has all of the rebase changes. I rebased again on main to fix the manifest issue, but I guess that messed up everything in the pr. you can rebase again if we want to use that branch or we can switch (again lol) to the new new rebased branch

[kheina]

fixed that issue. (finally) and another asset url issue too. these are built from e778b75

blue-blocker-firefox-0.3.0.zip
blue-blocker-chrome-0.3.0.zip

[kheina]

I'm dumb, I've been copy and pasting the same manifest for firefox as the first, and the hashes broke everything. here's the updated one from e778b75

blue-blocker-firefox-0.3.0.zip

[kheina]

if I find no issues, I'll merge to main and upload these tomorrow. holy shit you guys, typescript is happening!!

[kheina]

I thought of a way to make indexed db work by using the service worker to make all accesses to the db and also fixed the external message listener for external addon integrations

built from 5f0105a
blue-blocker-firefox-0.3.0.zip
blue-blocker-chrome-0.3.0.zip

[kheina]

gonna start posting these on the pr itself for simplicity