-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Prettify Timeline #10972
Prettify Timeline #10972
Conversation
@Sorien Please fix lint. |
b26f3c5
to
51e2511
Compare
Thank you for PR I will try and review later. If you aren't sure how to fix the failing tests you can add me as a collaborator and I can fix them |
@mrsdizzie I added you as a collaborator, it would be great if you could fix these tests :) |
Thanks I'll take a look -- also its best to avoid force pushing to PRs (it will mess up reviews and makes it harder to see certain changes) |
I was just fixing random things and rebasing multiple times, I'm mostly done, for now. |
Codecov Report
@@ Coverage Diff @@
## master #10972 +/- ##
=======================================
Coverage 43.38% 43.38%
=======================================
Files 597 597
Lines 84526 84526
=======================================
+ Hits 36668 36675 +7
+ Misses 43329 43327 -2
+ Partials 4529 4524 -5
Continue to review full report at Codecov.
|
@@ -139,7 +139,7 @@ func testNewIssue(t *testing.T, session *TestSession, user, repo, title, content | |||
htmlDoc = NewHTMLParser(t, resp.Body) | |||
val := htmlDoc.doc.Find("#issue-title").Text() | |||
assert.Equal(t, title, val) | |||
val = htmlDoc.doc.Find(".comment-list .comments .comment .render-content p").First().Text() |
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.
thx for updates, I removed this class couse it's setting max-width: 650px;
(semantic) later it was overridden with gittea styles to 100% but it's not correct, but it seems that max-width: inherit;
is working as expected so I'll recheck in few more browsers and reintroduce that comments
class
IE/Edge sucks :)
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.
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.
Thats ok imo we aren't really using the comments class here as it is intended by fomantic since this is more of a timeline of various events than a comment response thread on a blog
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.
fomantic can be customized by https://fomantic-ui.com/usage/theming.html so we should be able to override this variable like Sorien@7afe937 to my knowledge it should be working but it's not :/
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.
Fomantic CSS is currently not being custom-built but copied because of a outstanding issue, see #10655. We'll be able to custom-build again with their next release, but still waiting on it.
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.
Or to be slightly more correct: Custom build does run but we copy the full CSS file over the custom version with that workaround. JS is still kept as custom build.
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.
+1
sync with master
I'd like to override some default Fomantic-UI variables. I have tried it according to their website but nothing works :/ ... is there anybody responsible for UI? |
Unfortunately, we can not currently build custom fomantic CSS because of workaround #10655. I plan to remove it with the next fomantic release that includes the very important fix fomantic/Fomantic-UI@7fd3f79. |
I guess we could runtime-patch fomantic with fomantic/Fomantic-UI@7fd3f79 if it's really important. |
@silverwind it is not so important for this pr but removing I have prepared some other changes that are counting with building custom Fomantic |
</div> | ||
<div class="ui attached segment"> | ||
<div class="detail"> | ||
<span class="text grey has-emoji">{{.Content}}</span> |
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 should be black, else all review comments are grey
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.
there is much more such things, like 4 different styles for author's name
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 don't think I understand, this styling is just for the content not the author name
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.
Is it something that is changed by this PR? it was just copied, as you can see here https://github.com/go-gitea/gitea/pull/10972/files/bf084000712e45eb4c1b92bb5eac213634f8f57c#diff-7b9c057e968c3c88205ca2b63f0bfbfbL351
I was just pointing that there are inconsistencies all over the place...
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 was grey before, but it was also displayed in the timeline before and not as its own comment. I think displaying it as a comment it should have black text like other comments.
Since this PR is about making lots of changes to the look it is ok to change things from how they were before if you think they will look better another way. If you think something seems bad or wrong feel free to make/suggest a change
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'm afk for a few days, if you can fix it, simply, by removing grey
class pls push to this branch you should still have rights
I'll try to fix some more things in further PRs
I think it is ok to not use the fomantic comments class to contain everything here-- it actually does very little itself: And we are already heavily modifying individual comments/avatars css and not using other intended classes like author and metadata so I don't think it matters to ditch comments here as long as things look fine (and I think our timeline is a bit different than a collection of comments like on a blog which is the fomantic example: https://fomantic-ui.com/views/comment.html). I think timeline-items is more descriptive as well |
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.
Excellent job!
fix wrong conditions check in initIssueComments after go-gitea#10972
…1040) * fix some bug about Request review * fix ``CreateComment`` wrong using ,it will not work when use Sqlite * fix wrong js click event code , it will send wrong data when it has many choices Signed-off-by: a1012112796 <1012112796@qq.com> * Apply suggestions from code review Co-Authored-By: Lauris BH <lauris@nix.lv> * add getReviewerByIssueIDAndUserID fix wrong conditions check in initIssueComments after #10972 * call CI again Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
Co-authored-by: mrsdizzie <info@mrsdizzie.com>
…-gitea#11040) * fix some bug about Request review * fix ``CreateComment`` wrong using ,it will not work when use Sqlite * fix wrong js click event code , it will send wrong data when it has many choices Signed-off-by: a1012112796 <1012112796@qq.com> * Apply suggestions from code review Co-Authored-By: Lauris BH <lauris@nix.lv> * add getReviewerByIssueIDAndUserID fix wrong conditions check in initIssueComments after go-gitea#10972 * call CI again Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
it should looks like
fixes
#10864
replaces
a1012112796@5b7addb
Co-authored-by: a1012112796 1012112796@qq.com