Skip to content

Implementing issue 83 #84

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

Merged
merged 2 commits into from
Jul 23, 2019
Merged

Implementing issue 83 #84

merged 2 commits into from
Jul 23, 2019

Conversation

jonasjabari
Copy link
Member

Issue #83: Link Component is broken

Changes

  • fixed link component by removing the link_to helper from the link template
  • replace it with simple a tag
  • added specs

@cameronnorman
Copy link
Collaborator

cameronnorman commented Jul 18, 2019

@jonasjabari Would this possibly solve the anchor issue? I doubt it but thought I should ask before I attempt to fix it this evening

Copy link
Collaborator

@cameronnorman cameronnorman left a comment

Choose a reason for hiding this comment

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

I am happy with the code here and have tested it. Maybe add this to the link documents

Example 5

This example renders a link with a get request to an address with an anchor.

div id: "foo", class: "bar" do
  link path: "#anchor" text: "Go to the anchor"
  5.times do |i|
    br do ; end
  end
  div id: "anchor"
    plain "I'm an anchor point the link scrolls to"
  end
end

returns

<div id="foo" class="bar">
  <a href="#anchor">Here</a>
  <br />
  <br />
  <br />
  <br />
  <br />
  <div id="anchor">I'm an anchor point the link scrolls to</div>
</div>

@jonasjabari
Copy link
Member Author

I need to test this again. A similar approach didn't work for me. I used the latest chrome browser, did you use a different browser?

@cameronnorman
Copy link
Collaborator

Yeah I used firefox

@jonasjabari
Copy link
Member Author

Ok, then #4 might be only chrome browser related. but this PR aims to resolve #83
Do you have any feedback concerning the implemention towards #83 ?

If not, may you approve the PR?
We can than discuss #4 in its issue. :)

@jonasjabari jonasjabari merged commit 716c548 into develop Jul 23, 2019
@pascalwengerter pascalwengerter deleted the implementing_issue_83 branch July 29, 2019 17:12
@jonasjabari jonasjabari added this to the 0.7.1 milestone Aug 1, 2019
@jonasjabari jonasjabari mentioned this pull request Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants