Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look into Draft.js for interviewer notes #41

Open
ROODAY opened this issue Aug 7, 2020 · 7 comments
Open

Look into Draft.js for interviewer notes #41

ROODAY opened this issue Aug 7, 2020 · 7 comments
Assignees
Labels
enhancement New feature or request v3.2 Target Release - v3.2

Comments

@ROODAY
Copy link
Member

ROODAY commented Aug 7, 2020

Try looking up how to implement Firepad in React, see if it's viable. Ask a maintainer how it affects usage quota.

Otherwise just use Draft.js to make a text field for each interviewer (they only see they their own values, might be better that way)

@ROODAY ROODAY self-assigned this Aug 7, 2020
@ROODAY
Copy link
Member Author

ROODAY commented Aug 10, 2020

More I think about this the less I feel a collaborative text editor is worth the hassle. Lots of complexity for little benefit, much simpler to let interviewers write separately. Perhaps instead a private chat between interviewers/only visible to interviewers? Could be a simple pub-sub that doesn't store anything except the last message? or deletes all the messages once the session closes

@ROODAY
Copy link
Member Author

ROODAY commented Aug 10, 2020

Also look into how draft.js stores rich text, and if it can be stored in firebase

@ROODAY ROODAY changed the title Try using a collaborative text editor for interviewer notes Look into Draft.js for interviewer notes Aug 26, 2020
@ROODAY
Copy link
Member Author

ROODAY commented Aug 26, 2020

Honestly even a chat window seems unnecessary, as people can just use messenger/other chat platforms. Just focus on using draft.js for rich text notes for now.

@ROODAY ROODAY added the enhancement New feature or request label Aug 26, 2020
@vitorvicente
Copy link
Member

Tested, doesn't seem to work properly? Also not a major change tbh, so closing this.

@ROODAY
Copy link
Member Author

ROODAY commented Jan 17, 2022

@vitorvicente Interested as to what the issues were, simply because I just used it for another project last month haha so I might be able to help debug

@vitorvicente
Copy link
Member

Firebase didn't seem to save it properly somehow

@vitorvicente vitorvicente added the v3.0 Target Release - v3.0 label Jan 17, 2022
@vitorvicente
Copy link
Member

Re-Opening and focusing on this in 3.2

@vitorvicente vitorvicente reopened this Jan 17, 2022
@vitorvicente vitorvicente added v3.2 Target Release - v3.2 and removed v3.0 Target Release - v3.0 labels Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v3.2 Target Release - v3.2
Projects
None yet
Development

No branches or pull requests

2 participants