Skip to content
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

[Secret Handshake] Fix formatting issue in admonition #2286

Closed
wants to merge 1 commit into from

Conversation

safwansamsudeen
Copy link
Contributor

There's a note which is looks incorrect in the UI. I think this change will solve it.
image

This is a basic PR, so I have not discussed it in the forum beforehand.

@safwansamsudeen safwansamsudeen requested a review from a team as a code owner June 8, 2023 10:35
@github-actions
Copy link
Contributor

github-actions bot commented Jun 8, 2023

Hello. Thanks for opening a PR on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.


Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

@github-actions github-actions bot closed this Jun 8, 2023
@kytrinyx
Copy link
Member

kytrinyx commented Jun 8, 2023

Thanks @safwansamsudeen.

It looks correct to me in the browser on the Ruby track (https://exercism.org/tracks/ruby/exercises/secret-handshake):
Screenshot 2023-06-08 at 1 37 37 PM

Which track are you looking at where it is broken?

@safwansamsudeen
Copy link
Contributor Author

safwansamsudeen commented Jun 8, 2023

Python - is this perhaps track specific?

EDIT: perhaps it's because of the instruction append.

A second edit: seems not, because even JS formats it like this.

@MatthijsBlom
Copy link
Contributor

MatthijsBlom commented Jun 8, 2023

This was fixed in #2238; the fix just hasn't been pulled yet by some tracks.

@safwansamsudeen
Copy link
Contributor Author

@kytrinyx Upon looking around, it seems both Python and JS lack the blank line between the link text and the link url.

You've committed this only on March 27th - perhaps the tracks haven't synced the change yet?

Sorry for the confusion - I originally opened this in Python, was redirected here, and then failed to see that there was a blank line difference in this version and Python's.

@safwansamsudeen safwansamsudeen deleted the patch-1 branch June 8, 2023 12:20
@kytrinyx
Copy link
Member

kytrinyx commented Jun 8, 2023

@safwansamsudeen this makes sense. The fix would be to run bin/configlet-fetch in the Python and JS repos, and then bin/configlet sync --update --yes --docs to update any instructions that have fixes from the upstream. --metadata

@BethanyG
Copy link
Member

BethanyG commented Jun 8, 2023

@kytrinyx @safwansamsudeen - my apologies. I had forgotten that this was part of exercism/python#3423, which is on hold by Erik, due to concerns that it would re-queue a bunch of Python solutions for retest unnecessarily.

Copy link
Member

@SleeplessByte SleeplessByte left a comment

Choose a reason for hiding this comment

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

See rejection message below

@MatthijsBlom
Copy link
Contributor

MatthijsBlom commented Jun 8, 2023

@SleeplessByte I actually expect this PR to break the rendering in just another way. See this forum thread.

Copy link
Member

@SleeplessByte SleeplessByte left a comment

Choose a reason for hiding this comment

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

Sorry I reviewed the opposite diff which I thought was moving the link inside the admonition.

There is nothing wrong with this markdown and this PR should remain closed.

If tracks have broken admonitions, they should sync with the problem specs. I think the JavaScript track is one of them like mentioned.

configlet can help here.

@SleeplessByte
Copy link
Member

SleeplessByte commented Jun 8, 2023

@SleeplessByte I actually expect this PR to break the rendering in just another way. See this forum thread.

Thank you for that. I just rejected this.

I've ran it myself and the old (current) markdown is correct. This PR is invalid.

The problem here was that the GitHub app did NOT show me the closed PR or other messages until after i read your message (via notification).

@safwansamsudeen
Copy link
Contributor Author

safwansamsudeen commented Jun 9, 2023

Nice to see this issue understood, thanks to everybody!

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.

5 participants