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

github.yml:123-127: advisories.yml is broken. We can't... #57

Open
0pdd opened this issue Jun 26, 2024 · 4 comments
Open

github.yml:123-127: advisories.yml is broken. We can't... #57

0pdd opened this issue Jun 26, 2024 · 4 comments
Labels
bug Something isn't working pdd

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jun 26, 2024

The puzzle 35-caa80163 from #35 has to be resolved:

# @todo #35:45min advisories.yml is broken.
# We can't compile an Open API spec with advisories.yml due to this error:
# -attribute (get).responses.200.content.'application/json'.schema. is not of type `object` (./paths/advisories.yml).
# This issue is critical, since it potentially affect all the endpoints
# containing same structure. Don't forget to remove this puzzle.

The puzzle was created by @rultor on 26-Jun-24.

Estimate: 45 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Copy link

@0pdd thanks for the report, here is a feedback:

  • The todo message does not provide enough context about the issue. It just states that there is an issue with the advisories.yml file, but it does not specify what the issue is or how it affects the functionality of the application.

  • The message also uses informal language, such as "Don't forget to remove this puzzle." This may not be clear to everyone who reads the message, and it adds an unnecessary tone to the message.

  • The todo message does not provide any guidance on how to fix the issue. It would be more helpful if the message included some suggestions on how the issue can be resolved.

In summary, the todo message could be improved by providing more context about the issue, using more formal language, and offering suggestions on how the issue can be fixed.

Please fix the bug report in order it to get resolved faster.
Analyzed with Phind/Phind-CodeLlama-34B-v2

@0pdd
Copy link
Collaborator Author

0pdd commented Jun 26, 2024

@0pdd thanks for the report, here is a feedback: * The todo message does not provide enough context ...

I see you're talking to me, but I can't reply since I'm not a chat bot.

@h1alexbel
Copy link
Owner

@l3r8yJ can you take this one?

@h1alexbel
Copy link
Owner

h1alexbel commented Jun 26, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pdd
Projects
None yet
Development

No branches or pull requests

2 participants