Merge develop into feature with updated package.json settings #340
Conversation
remove Harmony update About with Team 2023's information
Fix local -> Develop
Test if develop branch can merge into Prof.Pruim's new feature branch
…evelop Merge updated-evening-schedule into develop
…ntoReadme Update README.md to include documentation
|
Is there a reason we haven't merged this branch into develop? I'm ready to do some scheduling work to help test all the changes. |
We created another branch from Prof. Pruim's feature branch and worked with that branch last Thursday to avoid changing Prof. Pruim's code. We merged develop into the new branch then merged the new branch back to develop to ensure nothing's broken, but then it seemed like the new feature wasn't working quite right and I'm not sure if Prof. Pruim has fixed that yet. If so we can merge this PR so you can do some testing. |
|
Ah, I remember. I had the impression that Randy had sorted that problem out. |
…s with multiple meeting times
…-format Feature/update scheduling format
Merging code from both Sophia and Faeren's branches into the Develop Branch
Update package.json
Develop update about 2024
- Moved external user documentation to the About and Help pages. - Distributed internal documentation between the root README (project-general development philosophy) and the Schedulizer client README (client-specific workflows)
Documentation cleanup and deployment test
Finished updating internal and external documentation
- configured Corepack and pnpm to set the correct versions of Node and pnpm - made final edits to the client workflow documentation - fixed the versions for 3 npm packages so that the system compiles and runs - fixed Sam's image All the npm package versions will need to be revisited and, perhaps, updated.
Fixed versioning issues
…bers add 2024 team members
…bers added 2024 proposal and status report
…bers correct the AboutPage link
No description provided.