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

docs: add committing style guide and fix typos (#244) #246

Merged

Conversation

WaltherTrgovac
Copy link
Collaborator

I have added the link for the committing style guide and fixed some typos.

@tstorek
Copy link
Collaborator

tstorek commented Mar 6, 2024

@WaltherTrgovac I just recognized that you changed, e.g. devive to 'device' in the examples. This wasactually on perpose to highlight it when converting to markdown.

@WaltherTrgovac
Copy link
Collaborator Author

I see what you mean, but .md and .py are two separate files, so the .md file stays unchanged. But if you want, I can revert the changes. Besides that, my idea was to make all the #ToDo comment sections and therefore .md files written in full sentences. And other comments I would leave as they are.

@tstorek
Copy link
Collaborator

tstorek commented Mar 7, 2024

I see what you mean, but .md and .py are two separate files, so the .md file stays unchanged. But if you want, I can revert the changes. Besides that, my idea was to make all the #ToDo comment sections and therefore .md files written in full sentences. And other comments I would leave as they are.

That's totally correct. However, we used to have a parser to generate the *.md from *.py. Not sure if it still exists ;)

@WaltherTrgovac
Copy link
Collaborator Author

I assumed that so I think it is better to leave them as it was, I will revert the changes.

@WaltherTrgovac WaltherTrgovac requested a review from Maghnie March 18, 2024 10:13
Copy link
Contributor

@Maghnie Maghnie left a comment

Choose a reason for hiding this comment

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

Thanks for the updates!

CONTRIBUTING.md Outdated

## Unit-Tests
Espacially when creating new functions or classes, you have to add a unit-test function.
Especially when creating new functions or classes, you have to add a unit-test function.
Open the `test_module.py` file in the `\tests`-directory and add a function to the class `TestModule`with a name like `test_my_new_function`. If you create a new module, you have to create a new `test_my_new_module.py` file and follow the existing structure of the
Copy link
Contributor

Choose a reason for hiding this comment

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

This wording makes it sound like there's a test_module.py file already

@djs0109 djs0109 self-requested a review April 23, 2024 12:23
@djs0109
Copy link
Contributor

djs0109 commented Apr 23, 2024

@Maghnie It looks good to me. You can merge if it also looks good for you now :)

@WaltherTrgovac WaltherTrgovac merged commit 49278e5 into RWTH-EBC:master Apr 23, 2024
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