Modifications for MVP readiness.

General guidelines are below.

addEvent form can combine "date" and "startTime" into a single date object key-value pair ("seedDate" in the schema) for the "seed" date before storing it in MongoDB (reference "date" in current dummy JSON)

We will be able to calculate recurring events based on the time and day of the seed date

Can remove or comment out endTime for MVP purposes

endDate should be added to the addEvent form and schema for the final end date of the event (greyed out or hidden if not recurring)

Using this format: https://github.com/fullstack-hy2020/create-app

Task should be started shortly after we do the add-event-form merge, but you can start to familiarize yourself with the formatting required.

@Caleb-Cohen you can include a link to the "CONTRIBUTING.md" in "README.md" as well.

Returning error post login. Looks like it has something to do with duplicate usernames into the schema. The only user in the database is my user.

2022-11-23 20:51:21.596: /var/task/node_modules/mongodb/lib/core/error.js:59
    return new MongoError(options);
           ^

MongoError: E11000 duplicate key error collection: test.users index: userName_1 dup key: { userName: null }
    at Function.create (/var/task/node_modules/mongodb/lib/core/error.js:59:12)
    at toError (/var/task/node_modules/mongodb/lib/utils.js:130:22)
    at /var/task/node_modules/mongodb/lib/operations/common_functions.js:258:39
    at handler (/var/task/node_modules/mongodb/lib/core/sdam/topology.js:961:24)
    at /var/task/node_modules/mongodb/lib/cmap/connection_pool.js:352:13
    at handleOperationResult (/var/task/node_modules/mongodb/lib/core/sdam/server.js:567:5)
    at MessageStream.messageHandler (/var/task/node_modules/mongodb/lib/cmap/connection.js:308:5)
    at MessageStream.emit (node:events:527:28)
    at processIncomingData (/var/task/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
    at MessageStream._write (/var/task/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
    at writeOrBuffer (node:internal/streams/writable:389:12)
    at _write (node:internal/streams/writable:330:10)
    at MessageStream.Writable.write (node:internal/streams/writable:334:10)
    at TLSSocket.ondata (node:internal/streams/readable:754:22)
    at TLSSocket.emit (node:events:527:28)
    at addChunk (node:internal/streams/readable:315:12) {
  driver: true,
  index: 0,
  code: 11000,
  keyPattern: { userName: 1 },
  keyValue: { userName: null }
}

Task

• Fork the development branch
• Investigate what is causing this error
• Implement fix and pull request to development branch

With PR #78 The model has changed and JSON needs to be updated for testing.

Just needing to put down a note for myself to assess the event model. We will need to add an end date again.

Add an example .env file that isn't ignored by git.
The file will contain placeholder information for the developers to reference when creating their .env file.

Creating an issue for creating user schema.

To test assigning/labeling/project adding.

Will be deleted when tests are done.

A work in progress, managed to refactor some of the code and divide into sub folders, add node engines for specific nodejs version
to 16.10.0

Please provide a summary of the feature
Title is satisfactory

Are there any potential issues you foresee with this feature
Confirm MongoDB is accepting the updated model.

Is this feature related to any current or past issues? Please provide the #
Add event form: #82

If you're interested in working on this feature, please comment so you can be assigned

Please provide a summary of the feature
Explore and implement date package managers like Date-fns to handle date calculations and localizing time to users.

Are there any potential issues you foresee with this feature
Plenty. Date and time conflicts, how will date-fns handle dates that cross day boundaries, etc.

Is this feature related to any current or past issues? Please provide the #
addEvent form data and event.js schema adjustments determined while working on calendar view #92

If you're interested in working on this feature, please comment so you can be assigned

Auth link no longer working on cyclic.

Today we're focusing on removing Binary Upload Boom remnants that are no longer functionally necessary for Together. We felt this was a good opportunity to have some of the newcomers get more familiar with the project structure.

Task:

• Fork the Refractor branch
• Remove files and code lines related to
• PR back to Refractor Branch

Binary Upload Boom (BuB) is a template provided by Leon and functions as a social network CRUD application. CRUD stands for create, read, update, delete and BuB is capable of applying that functionality to posts of photos. There is some functionality left over from BuB template that Together does not need.

Here are some examples:

• The entire Post Model
• The entire Home in controllers
• router.get("/profile", ensureAuth, postsController.getProfile); on line 12 in main.js
• app.set("view engine", "ejs"); on line 23 in server.js

Exception:

• Do not touch Cloudinary. We do not currently use it, but it's nice to have.

There will be multiple people working on this quickly. Please commit and PR in an organized and timely fashion, but also be sure to pull prior to a commit.

I'll take this on.

This issue is part of the ongoing Quality of Life updates #29.

Task

• Remove views folder which contains all the EJS files.
• Remove public folder which contains BuB favicons and other assets.

CONTRIBUTING.md needs a refactor.

Placeholder for discussion

I'll update the JSON with @code2244. @InstincDev & @MattewBozin can you update the form?

Please provide a summary of the feature
Currently, the calendar only shows the time and event title. Users need to be able to see more event information like description, who's coordinating the event, and where the event will be. We will call this the event-details views

Additional context
Natalie provided a really good design here that can be used later, the only thing missing is the user that created the event is included.

Design does a great job, but we do not need editing for the MVP, focus on core-functionality. We will make it look nice and add complexity later.

If you're interested in working on this feature, please comment so you can be assigned

Discussed in #88

Summary

Combine both frontend and backend dependencies into one package.json at the root folder.

root
|
+-- ../              # existing files and folders
|
+-- client           # frontend related files and folder
|
+-- server           # backend related files and folder
|
+-- .eslintignore    # ignore files/folders that does not require linting
|
+-- .eslintrc.js     # linting configuration
|
+-- .perttierrc      # prettier configuration
|
+-- .package.json    # packages/dependencies for both client and server.

Please provide a summary of the feature
When the user is completing the add-event form have the form use the logged-in user's discord display name instead of having it manually entered.

Are there any potential issues you foresee with this feature
I could foresee some issues with how the backend interacts with the frontend.

Is this feature related to any current or past issues? Please provide the #
Related to discord Auth: #21
Add-event form: #82

@WinstonHall please comment so I can assign it.

This issue will be used for tracking any Quality of Life update/Improvement. An issue should be created for each task referencing back to this issue. (Example: #30)

Task

• Update README to show examples of the prerequisites API keys needed for working with Backend. Create a .env.example in to config folder. #30
• Add a new scripts to package.json to reduce the amount of commands needed to run for getting started with the project. Add instructions to readme.
• Considering adding a skeleton page structure for routing e.g. Landing page, Calendar page so that other collbarator can focus on building out said pages without having to worry about needing to setup React core routing functionalities.
• Possibly add Eslint & Prettier to auto format code to keep consistency throughout codebase?
• Remove views folder which contains all the EJS files now that the Frontend is build in React.
• Remove Procfile.

Hey @Caleb-Cohen, do you approve of these Quality of Life update to the project? Is there anything that should be added or remove from the tasks?

• update Readme to be more clear
• add all tasks to project board

Please provide a summary of the feature
Only logged-in users should be able to complete the add-event form. The form can be hidden or just locked from submission. The choice is yours.

Are there any potential issues you foresee with this feature
I could foresee some issues with how the backend interacts with the frontend.

Is this feature related to any current or past issues? Please provide the #
Related to discord Auth: #21
Add-event form: #82

@WinstonHall - can you comment so I can assign you?

Task

• Convert the codepen template provided to React components

Questions

• Should it be a static UI at the current stage or are there any dummy data to populate the each day to show the events?
• Should the view folder be replaced with React (create-react-app) or add client folder dedicated for React?

We should be able to provide some dummy JSON data for the npm run devstart command to enable developers to test the code without needing discord auth or mongo secrets and keys

Summary

Currently the dev script in the client folder is pointing to the incorrect json file. We need to fix that by pointing back to the correct test json-server file and remove the z-code tutorial json file.

Tasks

Step 1

• Delete client/src/services/events.json.
• Update the client package.json file dev script path pointing to src/test/events.json.
• Test that the script work as expected.

Step 2

• Add new scripts to the root package.json file.
  Note: You want to add it under start-client script.

"start-mockServer": "npm --prefix client run dev",
"dev-concurrent-mockServer": "concurrently \"npm:start-client\" \"npm:start-mockServer\"",

• Test that the script work as expected.

Task

• Shows current months and can click for future months.

I like to work on this issue.

I'll take a shot at it :-D

This is an issue representing task 4 of issue #29

Add a React Router for routing between/adding new pages so that other collaborators would be able to add new pages with minimal setup.

• Add React Router and create a router in App.js that can route between pages.
• Create two dummy pages that can route between each other to demonstrate that it works and provide an example to contributors that want to create pages.
• Create a guide that shows other collaborators how to create new pages and get those pages set up with the Router. Post it as markdown in the comments of this issue.

Reserving for discussion.

This is an issue representing task 3 of issue #77

Task

• Re-organize files/folders to match Bulletproof React project structure.
• Configure the project to use absolute import; set to baseUrl to src and a global import of @feature following Bulletproof React guidelines.

Might have to update the model at the same time.

Fork from the Add-Event-Form branch. When completed, pull request into the Add-Event-Form not main. Instructions on how to contribute can be found here

Add //Please copy and paste this template into a new .env file instead of removing .example from the file name to the first line of the .env.example file.

Additionally, change the formatting of value pairs to match DB_STRING = YOUR_DATABASE_URI. Port does not need to be re-formatted.

test

This issue will be used for tracking all the task related to re-organizing the project structure. An issue should be created for each task referencing back to this issue. Example: This is an issue representing task {x} of issue #77

We will be using this starter repo as a guideline to re-organize the project structure: https://github.com/fullstack-hy2020/create-app

Note: Task should be started shortly after we do the add-event-form merge, but you can start to familiarize yourself with the formatting required.

• Create a server folder and move anything backend related into said folder. #69
• Combine and relocate all of the package.json, scripts and miscellaneous configuration to the root of the project. #96
• Improve React project structure using Bulletproof React as guideline. We need to discuss whether we should keep the folder name as frontend or change it to client. #83
• Refactor/fix the scripts so that it works with new project structure. #103

Summary

Update the root package.json file name and description.

Task

• Change name from binary-upload-boom to Together.
• Update the description to explain what Together is. A description can be found in the repo or in the Readme.md file.

To contribute

Fork from the refractor branch. When completed, make a pull request comparing to the refractor branch. Instructions on how to contribute can be found here. If there's any question you can ask here or over in the Together Discord thread.

Task

• Refactor login with Discord button into a component to improve project structure.
• Pass user data from React/Discord to backend.
• Create user within database on backend.

I would like to take a stab at this issue.

There are settings you can add making code submitted be locked out from finalizing any sorta merge to our repo.
Example - one of the settings just gates the code until a set number of people sign off on the changes.
There are a few more but I'm drawing blank on it atm.