mjrmyke / csci150project Goto Github PK

Provide a View Notes page based on the CSS for the editor.
Give an anchor to the relevant edit page.
I'll finish integrating the prototype once you're done.
additionally be sure to Be sure to {{define "viewNotes"}}

Feel free to work independently, but do not commit to develop for the time being.

Include a form with method POST that has the following

• Text Field Edit First Name , name = "first"
• Text Field Edit Last Name, name = "last"
• Textarea Edit Bio, name = "bio"
• Upload File Avatar, name = "avatar"

Include a prototype for generating the following, separate from the form.
Drop Down [Public, Protected, Private], name = "{{.ID}}" <- Was uneeded due to editor structure.

Reasoning-
Interacting with many notes through template is unwieldy so the hook will use an API call from the js side to actually change a note's security settings. But this will be done separately from the initial implementation.

similar to #19 , might be a good idea to collaborate.
additionally be sure to Be sure to {{define "editProfile"}}

https://github.com/mjrmyke/CSCI150Project/blob/Kenneth/parser/main.go

• Meets Desired Requirements
• Maintainable
• Passes Misc. Checklists

Requesting Merge: 0af6239
Kenneth into develop

12-2
MO WE FRI

Implement a prototype for editing notes through raw markdown. Should be able to be passed to a POST request.
will be based on #20
additionally be sure to Be sure to {{define "editRaw"}}

#20
@mjrmyke , that quill editor is absolutely great. I actually feel like my parser isn't needed. Welp, if someone else does it better and it's a service then it's best to use it right? :)
I'll put any faults I find under separate issues.

• Perform Integration
• Resolve Any Merge Conflicts from Pulls
• Determine Next Step

There is an unfortunate fault at the moment in that the avatar upload isn't working. We will likely have to exclude the feature from this iteration. But that isn't my decision, that power goes to @mjrmyke .

Specifically, the handler meant to handle it will break. Two different defects occur depending on if a file is uploaded or not.
If one is uploaded it fails and serves an empty page(redirect fails.)
If one is not uploaded our server returns an error.

You can reproduce the bug by uncommenting the code in POST_ProfileEdit.

Because we do use avatars I propose continuing to use the placeholder so that our page aesthetics do not break.

Be able to present the following information with some sort of template hook for the backend.(just use descriptive names, I can fix the hooks during integration.)

• List First Name,
• List Last Name
• List Bio
• List Avatar
• List Public and Protected Notes
• IF you are the user, also list private notes(assume cookie data will be accessible)

similar to #18 , might be a good idea to collaborate.

additionally be sure to Be sure to {{define "viewProfile"}}