Skip to content

Removed duplicates of debug.info() #1085

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ExtremePro11299
Copy link
Contributor

Changes

I ran into the debug.info() thing 3 times while scrolling. This should fix it. One of the duplicates had a different code sample that the other two, so I cut and pasted it into the one debug.info() that I made.

Checks

By submitting your pull request for review, you agree to the following:

  • This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
  • I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
  • To the best of my knowledge, all proposed changes are accurate.

@ExtremePro11299 ExtremePro11299 requested a review from a team as a code owner April 26, 2025 08:40
@github-actions github-actions bot added the engine reference Changes the Engine API Reference documentation label Apr 26, 2025
@IgnisRBX
Copy link
Contributor

Admitted that this is a bit unclear, but it's a factor of how library functions are output to docs. The three different "variations" of debug.info() are shown since they each expect a different set of parameters... note that it's either level, options OR function, options OR thread, level, options. So each of these is documented separately. Open to cleaning up aspects of each if necessary, but we'd prefer to keep all 3 variations.

Copy link

This pull request has been inactive for 14 days. If there's no activity in the next 7 days, it will be automatically closed. To keep it open, please comment or push new commits. Alternatively, add the label do-not-close to exempt it from auto-closing. 🫡 🙏

@github-actions github-actions bot added the stale label May 12, 2025
@ExtremePro11299
Copy link
Contributor Author

Anti-stale comment

@github-actions github-actions bot removed the stale label May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine reference Changes the Engine API Reference documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants