Open ClaytonNolen opened 10 months ago
This link goes into detail of how to install and setup Firebase into Javascript [https://firebase.google.com/docs/database/web/start]. This involves creating the database and ensuring that it will be updated in real time. More information to follow (7:05pm).
Following up, there are more subjects that give multiple in depth steps on how to complete:
Setting up the database today (attempt 1). Looking at tutorial resources and if the code can reflect changes in Firebase.
Currently reading and watching videos for Firebase set up with JS. JS and HTML files have been created and will be posted in the google drive until github repo is linked in the near future. Below are the current achievements:
Have added packages from Node.js and began to link script file, "package.json", with other files by using paths. However, error has occured:
claytonnolen@Claytons-MBP Capstone % npm run build npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /Users/claytonnolen/Capstone/package.json npm ERR! errno -2 npm ERR! enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/claytonnolen/Capstone/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
npm ERR! A complete log of this run can be found in: /Users/claytonnolen/.npm/_logs/2024-02-10T20_06_58_720Z-debug-0.log
WIll continue the debugging process and work towards the creation of our database.
In addition, I have created a folder in the drive labeled, "Hit by Bus". That way if I am hit by a bus everything I have done can be traced back and redone. I wish the best of luck to the bus that attempts to hit me.
The 'build' script we have created is having issues finding the file in our path. Code looks correct and will continue troubleshooting. Best course of action might be to redo the package dependencies. Will update thread soon.
SUCCESS - asset bundle.js was created and compiled with webpack.
Reason for error is unknown but I suspect that even though we coded our script, it was not reflected globally or in our terminal. After entering a debugging terminal and exiting out, the terminal was able to execute our commands successfully.
commands:
npm run // Shows what scripts you have
nom run
To troubleshoot go to the ./src/index.js file and change its code. After save the file. If successful the terminal will prompt you with this message:
I am happy to announce the front and back end between our Firebase project and Capstone programs are linked together and happily communicating live. Future work will be to connect my VS to the Git repo, create database values and test them, present the team with the updated details, and polish the current code.
Looking into connecting my VS to the github repo.
Have accidentally made a new repo with VS and trying to add it to the correct one.
When syncing the file I mistakenly deleted everything I have done so now I am going to redo it asap ◡̈ ... lovely
I restored the webpack files for our db but will need further assistance on github repo sync from Dr. Anthony.
Plan: Scorch Earth. Pull Git Repo. Redo DB Code.
Scorched Earth done and commit and push test successful. Made a new folder titled "misc" for license.
Github repo has successfully been committed and pushed with changes ◡̈
Reviewed code with Daniel and discussed webpack dependency.
Able to connect GitHub to VS Code and Clayton showed me how to get to Webpack. Need to figure out how to use it on Windows.
Firebase should be connected with our Webpack - will test at a later date. Done for the day.
Coming up with an error on pulling new changes but will continue to test what is going wrong.
Getting caught up with the database and everyone else changes.
Lots of changes have been done and I will need to discuss details tomorrow with teammates. Currently working on a test entity for the db. Will be working on the abstract later today if I finish, become bored, or too frustrated ◡̈
Code for collecting data should work but I am unable to test because of what others have pushed. Will continue adding features as drafts.
Have created an array to hole the attributes of a test user. These attributes currently include: Name, Age, Membership. These are subject to change and have been developing code in the index.js file. Have also made an add feature to populate database data and will shortly add a remove feature. I apologize for missing a 30 minute mark or two - I was in the zone.
Delete Button and Debugging features on the website under way
Deleted and Accepted Buttons for testing DB but need to talk to group on what was changed that affected our connection.
Issue was not having Vite installed. Working on installing it now and will see which file is connected to the database now.
Errors found in my code that are most likely from un-updated code
Working towards fixing the our Firebase: JS vs HTML vs Svelte (Start).
Found a video that I believe is going to help fix our issue and catch me up on what needs to happen: https://www.youtube.com/watch?v=3Q4fK1NdNMQ
Added TypeScript files guided by the video I am extremely confident will fix it!
Done with coding and believe to have fixed the db issue. (Week 3, 2:30, 1:15 today).
Continuing the development of Authentication.svelte so that I can check the database connection progress the project past database. (Start, 2:30 left).
I am lost at where to test and what to develop. I am worried that because everyone has pushed and added so much of their own dependencies and files that we have a tangled mess. Currently going to start a new folder, if it works I will migrate everyones work and connect it to Github. If it does not I might know enough of what we are missing to fix the issue and what we are missing. (3:00)
Installed tailwind and connection works. Looking much better than other github repo.
Enabled scalability into our svelte.config.js file for a color template that we will change later.
Linking our Firebase to firebase.ts file
Taking a break. Init firebase atm
Working on firebase.ts file
Changed made
Created Gym folder with user object. Done for the week
Looking into the practicality of how to get the database running with Javascript.