Replies: 2 comments 10 replies
-
|
Thanks for the detailed update on the current state of the project. I’d be happy to help with refactoring efforts to modularize the backend (separating routes, controllers, and services) to reduce duplication and make the codebase easier to maintain. I can also review PR #68 to help move the live stream functionality forward. Setting up pre-commit checks (like Husky) sounds like a good idea to prevent CI issues before pushing PRs — I can look into that as well if needed. Let me know where you'd prefer I start. |
Beta Was this translation helpful? Give feedback.
-
|
Well, yesterday I added a PR to make style.css more flexible and modular and less monolithic. I didn't do a prettier run or eslint on it so theres that but usually css code style issues don't happen very often It's also more maintainable and easier to add new things or debug. I also added a PR that fixes the index.html that had two layers of duplicate stuff. I'd suggest merging those soon. Well CodeByStella deleted their PRs for functionality without it getting merged. Just minor package issues causing CI to fail. Should have been through this already but 🤷♂️ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Well now, let's see how do I best describe the state of codestream as of Mid February 2026.
We've gotten up to the point where we've hit a lot of back and forth CI issues.
There's currently a number of open PRs that:
We're having issues due to several monolithic files like server.js and main.js
We should aim to be less monolithic so that changes by several contributors:
#68 needs review so I can get the last bit ot live stream functionality in
As still some measure of safety I'm only merging PRs that have at least 2 other approved reviews that show ✅ next to the reviewer on github. Won't need to do that so much when we have passing CI, passing tests, less monolithic structures, seoa
We will need to work on separating the frontend from the backend code. Use #77 #78
Then we can work on adding more to the backend and server and APIs. I created a bunch of issues marked TODO staring with issue #100 through #104 which would add more to the backend
Screenshots of the entire app need to go into #67 perhaps short videos or clips so we can document
There is still a ton of duplicate code in the repository due to the fact we're having so many problems with merge conflict's and monolithic structures etc. I don't even know if it will run probably? without major work?
There's been some AI contribution happening. We'll have to address that soon.
I'm okay with using AI to help debug this application but not so keen on using it for broad generation of code. Some small amount of generated Boilerplate code is okay though to reduce the overall amount of typing.required.
I merged some of the live functionality in PR #61 it will need #68 added to it in order for this project to become even slightly useable.
I'd also like to suggest we start doing preflight precommit procedures before we push a commit for PR. Maybe use husky?
@Ved178 @gbowne1 @shishir-21 @EdoAbarca @Haseebx162006 @glenjaysondmello
Beta Was this translation helpful? Give feedback.
All reactions