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

[#234] Empty line is supposed as stop for puzzle description #236

Merged
merged 3 commits into from
Jan 20, 2024

Conversation

pnatashap
Copy link
Contributor

  1. Empty comment line is supposed to be as end of the puzzle description
  2. If comment contains space symbol it is still considered as puzzle description

@pnatashap
Copy link
Contributor Author

@php-coder @yegor256 please take a look

There is a separate issue about missing description for multiline puzzles, so haven't touched it yet #224

@yegor256
Copy link
Member

@rultor merge

@rultor
Copy link
Collaborator

rultor commented Jan 20, 2024

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit 7c3a95d into cqfn:master Jan 20, 2024
5 checks passed
@rultor
Copy link
Collaborator

rultor commented Jan 20, 2024

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 3min)

'
// TODO: #46 task description
//
// second line after empty line is a part of the puzzle in case of space exists
Copy link
Contributor

Choose a reason for hiding this comment

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

Line 145 also has a leading space after an empty line, but it isn't part of puzzle text. How this line is different?

Copy link
Contributor

@php-coder php-coder Jan 22, 2024

Choose a reason for hiding this comment

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

Oh, I see it now: on line 159 there is a trailing space.

Could we have a better rules for distinguishing one type of the comments from another? The current one seems like a subject for future confusions of our users.

/cc @yegor256 WDYT?

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.

4 participants