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
feat: Implement add post UI [BD-03][TNL-1618][BB-2970] #6
feat: Implement add post UI [BD-03][TNL-1618][BB-2970] #6
Conversation
Thanks for the pull request, @0x29a! I've created BLENDED-607 to keep track of it in Jira. More details are on the BD-03 project page. When this pull request is ready, tag your edX technical lead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good for the most part, however I think we need to keep in mind that this UI won't just be used for adding posts, but for editing them as well.
While that is out of scope of this PR, I think it can affect how key variables are named.
src/discussions/posts/data/slices.js
Outdated
@@ -36,6 +36,7 @@ const coursePostsSlice = createSlice({ | |||
topicPostMap: { | |||
// Mapping of topic ids to posts in them | |||
}, | |||
postAddingInProgress: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be renamed to: showPostEditor
or similar
e618aca
to
be0c362
Compare
a8d5dee
to
794ec44
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left a few general comments, other than that it looks OK.
👍
- I tested this: tested on devstack
- I read through the code
- I checked for accessibility issues
}, | ||
}); | ||
|
||
export default messages; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems the general convention for edX projects is to use camel case here as well. Could you update these message keys accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found even dot notation. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that guidance in frontend-platform
’s doc is a bit antiquated. Using a short camelCase string for the object key is fine, so long as the id
is also globally unique in the MFE. I have seen these too in the code but uts just easier to read than remembering some big long dot-delimited string.
Is there a Jira related to this? if not, can you create that? |
@awaisdar001 Sure. There is an existing ticket. @0x29a will update the PR to include those details. |
@0x29a Any updates on this PR? |
Hi @asadazam93, I'm going to rebase & test this today, or on Monday. I will ping you once this is ready for final review. |
b9a574c
to
43ff126
Compare
@asadazam93, this is ready for edX review. |
@0x29a I don't have access to the attached tickets and there is no description provided as context to the done work. can you please add some description to the PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add PR description explaining purpose of PR.
remove font awesome icon with paragon icons.
fix lint error
14a9074
to
b5fc44f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't had the Figma designs related to this PR before, now I get it and feel like even if this PR is only related to UI still its not even close to mock designs
https://www.figma.com/file/LVFnO9oRHYiamoicZuXDAC/Discussion-page?node-id=1918%3A57140
can you please confirm about that?? @xitij2000 @0x29a
Okay I think I was looking at old screenshot. the new one looks fine to me. never mind |
b5fc44f
to
47c294c
Compare
@xitij2000 any update on this one? |
|
@xitij2000 yes of course I did, I will check again can you please tell me any backend setting that should be there for running? I am running latest studio code |
https://www.figma.com/file/LVFnO9oRHYiamoicZuXDAC/Discussion-page?node-id=1918%3A57140 The view is visible now, the design does not match Figma, the upper action bar I am not sure if that is part of ticket but that's completely different. apart from that the Add a post section is missing bug/issue option and the post editor is missing all the editing options and design does not contain follow this post and post anonymous options here. Figma link is attached |
I think you have the wrong link there. The design I'm following is here: https://www.figma.com/file/LVFnO9oRHYiamoicZuXDAC/Discussion-page?node-id=1918%3A53114 I think it's a bit confusing because there are a few similar but different views around floating around. The bug/issue feature will come in a far future milestone. The post editor is part of a different PR since we need to investigate how exactly to integrate it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this PR is purely related to UI design. So there are many differences between current UI design and Figma Design.
47c294c
to
9d8da9f
Compare
65610ca
to
f8e4d16
Compare
@awais-ansari, I think I've addressed all comments. Also, I've updated the screenshot in the PR description. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
@mehaknasir, @awais-ansari thank you very much for thorough review! |
* Changes copied from Michael's PR * Modifications for URL scheme * renamed variable * added prop type * updated variable name * fix(i18n): update translations * added newline * updated variable name Co-authored-by: edX Transifex Bot <learner-engineering@edx.org>
This PR contains the UI for adding of post.
JIRA tickets:
Screenshots:
Testing instructions:
http://localhost:2002/discussions/course-v1:edX+DemoX+Demo_Course/
.Reviewers