Skip to content

fix: footer Expand area below last footer line #5706

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

Closed
wants to merge 12 commits into from

Conversation

Raunaksingh100
Copy link
Member

@Raunaksingh100 Raunaksingh100 commented Nov 21, 2020

Fixes #5705

Short description of what this resolves:

footer Expand area below last footer line

screenshot

now

Checklist

  • I have read the Contribution & Best practices Guide.
  • My branch is up-to-date with the Upstream development branch.
  • The acceptance, integration, unit tests and linter pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@vercel
Copy link

vercel bot commented Nov 21, 2020

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/eventyay/open-event-frontend/ffxdoqqpd
✅ Preview: https://open-event-frontend-git-patch-6.eventyay.now.sh

@Raunaksingh100
Copy link
Member Author

@mariobehling and @iamareebjamal can you review this pr

@@ -14,3 +14,7 @@ a.link-item {
.leaflet-container {
height: 300px;
}

div#ember126 {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just merged a PR and this changed to ember234. Tomorrow it might be 132, the next day it'll be 342. We don't want to merge a PR to fix this every day. We want a solution which works once and for all

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i will fixed it

@iamareebjamal
Copy link
Member

@Raunaksingh100 Thankfully GitHub has a notification system, we know when someone creates a PR, you don't need to comment for us to know. This is probably 5th time I had to tell you this. No, thanks, we don't need comments to know that you have created a PR

@codecov
Copy link

codecov bot commented Nov 21, 2020

Codecov Report

Merging #5706 (898a765) into development (975272a) will decrease coverage by 0.05%.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff               @@
##           development    #5706      +/-   ##
===============================================
- Coverage        23.62%   23.57%   -0.06%     
===============================================
  Files              510      510              
  Lines             5417     5430      +13     
  Branches            59       59              
===============================================
  Hits              1280     1280              
- Misses            4122     4134      +12     
- Partials            15       16       +1     
Impacted Files Coverage Δ
app/components/widgets/forms/social-link-field.ts 60.00% <0.00%> (-15.00%) ⬇️
app/services/cache.ts 64.15% <0.00%> (-5.67%) ⬇️
app/routes/index.js 78.57% <0.00%> (ø)
app/components/public/side-menu.js 0.00% <0.00%> (ø)
app/controllers/admin/events/list.js 0.00% <0.00%> (ø)
app/components/forms/orders/attendee-list.js 0.00% <0.00%> (ø)
app/controllers/events/view/tickets/orders/list.js 0.00% <0.00%> (ø)
.../components/forms/wizard/sessions-speakers-step.js 0.00% <0.00%> (ø)
app/mixins/ember-table-route.js 80.00% <0.00%> (+5.00%) ⬆️
app/controllers/events/list.js 23.07% <0.00%> (+13.98%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 975272a...fdd9559. Read the comment docs.

@@ -14,3 +14,7 @@ a.link-item {
.leaflet-container {
height: 300px;
}

.floating.labeled.grey.search.icon.mini.button.ui.dropdown.ember-view.upward.active.visible {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tomorrow I will change one class on the element and it'll stop working

Copy link
Member Author

@Raunaksingh100 Raunaksingh100 Nov 21, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tomorrow I will change one class on the element and it'll stop working

i am doing the wrong things the purpose of the issue is ""footer Expand area below last footer line""
i will fixed

@Raunaksingh100 Raunaksingh100 changed the title fix; Footer: Expand area below last footer line fix: footer Expand area below last footer line Nov 21, 2020
@auto-label auto-label bot added the fix label Nov 21, 2020
@mariobehling
Copy link
Member

You need to implement the change below the absolute last line. Do not change anything in between the footer. Add space on the very end.

@@ -102,6 +102,7 @@
</div>
</div>
<div class="ui inverted section divider"></div>
<br>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't do it like this

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you little guide ma what is the purpose of the issue I am little confused

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to add/expand the space after the last line, use inline styling.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i updated the code

@@ -101,7 +101,7 @@
</div>
</div>
</div>
<div class="ui inverted section divider"></div>
<div class="ui inverted section divider"style="margin-bottom: 40px!important;"></div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mb-4

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mb-4

I added the code can you review

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not working AFAIK

Copy link
Member Author

@Raunaksingh100 Raunaksingh100 Nov 25, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

already update the code but,

@iamareebjamal can you tell me what is the purpose of writing the i am working on this issue if some gets solutions can make pr on any issue it means we are wasting out time

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you tell me what's the purpose of reviewing PRs and writing "It's not working AFAIK" and not getting any follow up on that?

@Raunaksingh100
Copy link
Member Author

@mariobehling i fixed the bug can you review

cggvuhh
cggvuhh previously approved these changes Nov 25, 2020
@divyamtayal divyamtayal mentioned this pull request Nov 25, 2020
5 tasks
cggvuhh
cggvuhh previously approved these changes Nov 25, 2020
@iamareebjamal
Copy link
Member

@Raunaksingh100 This is your last commit 3 days ago 6044ccc (#5706)

Which was not working. I commented that it is not working. You did not follow up. Revert to this commit, and show me that it is working. I'll merge this PR, otherwise I'll merge #5745

You can't just stay silent on follow up and then complain that your non-working PR was not merged and then copy the solution from a working PR 3 days later. Why did you not follow up on my comment for 3 days?

If you had the solution, why did you not fix the PR 3 days ago, why just now after someone else submitted a working PR?

@iamareebjamal
Copy link
Member

#5706
image

Your PR:
image

How can you possibly expect me to merge a PR which not only does not fix the issue, but also breaks the existing UI?

@iamareebjamal
Copy link
Member

I'm sorry, your work was based on the new PR which was created by @daretobedifferent18
Please follow up when asked for review. You can't expect no one to solve a basic issue if you don't reply or follow up on a PR for days. We want to optimize for issues being solved. Not replying or following up is a blocker and ties up the hands of other people who may fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Footer: Expand area below last footer line
5 participants