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

Add two topics to Documentation Tips and Tricks #392

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

Conversation

gohierf
Copy link
Contributor

@gohierf gohierf commented Feb 7, 2025

  • Resolving Imports from a Central common.resource File
  • Why is my non local variable "not found"?

- Resolving Imports from a Central common.resource File
- Why is my non local variable "not found"?
@d-biehl
Copy link
Member

d-biehl commented Feb 10, 2025

Nice! I’ll review it after RoboCon. Are you attending as well?

@gohierf
Copy link
Contributor Author

gohierf commented Feb 10, 2025

Nice! I’ll review it after RoboCon. Are you attending as well?

No not this year unfortunately.
However, I will be attending the concurrency workshop from Franz.

@d-biehl
Copy link
Member

d-biehl commented Feb 25, 2025

He @gohierf, I revised the text for Resolving Imports from a Central common.resource File a bit, generalized it, and added it as a separate title under the Tips & Tricks section. And I included you as a co-author in the commit.

In the next few days, I will do the same with the variable topic.

The article hasn’t been uploaded to the RobotCode website yet; I’ll do that once everything is finished. However, you can already read the article here: https://github.com/robotcodedev/robotcode/blob/main/docs/04_tip_and_tricks/avoiding_a_global_resource_file.md
and I would appreciate your feedback.

Unfortunately, I won’t be able to merge your PR, because for security reasons I only allow commits with a public signature in the RobotCode repository. Security is taken rather seriously here; essentially, I want to make sure that a real person is behind the commit.

Check this out: https://docs.github.com/en/authentication/managing-commit-signature-verification

Thanks anyway, and you’re still mentioned ;-)

@gohierf
Copy link
Contributor Author

gohierf commented Feb 26, 2025

The new version, with your extensive edition is very thorough. I believe we can keep it like that!
Cheers

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.

2 participants