-
Notifications
You must be signed in to change notification settings - Fork 38
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
[FIX] Description Under Overview Action Showing null #39
Conversation
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.
@Nabhag8848 Thanks for your PR 🚀 Added some suggestions, can you please take a look ?
github/lib/repoDataMessage.ts
Outdated
let description: string | null = resData.description; | ||
|
||
if(description === null){ | ||
description = 'No description provided.'; | ||
} | ||
|
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.
Hey @Nabhag8848 , thanks for solving this for us. Works well 🚀 !
But maybe we can do something like this
const description = resData.description || 'No description provided.';
This will make sure that the description is const and is not updated before sending it to the main channel. Also it fits with the code style we have in this file and saves some lines.
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.
@Nabhag8848 Can this PR be extended to fix some other places where we are showing null values ?
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.
Yep! we can do that. Do you encounter any nulls, possibly i didn't encounter yet? if you have point me up.
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.
Hey, @samad-yar-khan . I found lot of places where there is asyncronous operation without await
and vice versa. should i make the commits within this PR? also we can merge my PR #41 branch with this one to make it bigger or we will include issue #47 within PR #41 later.
How should we proceed.
@Nabhag8848 Can you please remove the last commit and make a separate Issue / PR to explain the position if |
f7c9ab0
to
3a3d7b3
Compare
Thanks @samad-yar-khan and thanks for pointing out. done removing the same and learn the lesson, i should not commit changes without acknowledgement. |
@Nabhag8848 LGTM ! you can add the |
Issue(s)
Closes #38
Fixed Bugs
No description provided
text instead ofnull
when the repository doesn't have a description.