-
Notifications
You must be signed in to change notification settings - Fork 25
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
pdd does not recognize my puzzle #96
Comments
@nikolausm/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot! |
@nikolausm please, show the full text. What do you have before the puzzle and after? |
As requested, the second todo i‘ve added afterwards:
|
Job #96 is now in scope, role is |
Thanks for your contribution, @nikolausm/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2. |
Thanks for submitting this issue @nikolausm. I cannot replicate this issue because puzzles were generated successfully. This issue seems to have been fixed. Please close this issue @yegor256 |
Here is another case: $ cat > bug
# TODO: #85 Make custom callbacks
# TODO: #85 Check alert messages
# TODO: #85 Refactor methods
$ pdd
ERROR: bug; puzzle at line #1; Space expected at 2:6; make sure all lines in the puzzle body have a single leading space. Expected: It would be great to have 3 issues created. |
@mbao01 what do you think? |
Okay maybe the example above is a little bit too much, after all we can add new lines and this is what I did. But indented lines after the first comment are being removed by Here is a proposal. Treat non-interrupted comment blocks starting with a marker as issues until the first empty line or the beginning of the next code block: # TODO: #1 Issue title
#
# ^ if you need an empty line for aesthetics
#
# Everything here is added as
# an issue body
#
# ... still the issue body
# This comment is left in the code
def hello |
Hi @firedev thanks for catching this. Looks like an issue with the Works as expected ✅
|
Nice @firedev , this is a good proposal! Is it possible for you to create a new issue for this proposal? |
// @todo #3 This should a developed as a small service.
which refers to Ticked: HSHighStake/partner-dashboard#3
This sends me an email with the following content:
The text was updated successfully, but these errors were encountered: