-
Notifications
You must be signed in to change notification settings - Fork 69
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
Repo cleanup and maintenance #269
Repo cleanup and maintenance #269
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
As part of the clean up, perhaps also delete the file |
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some thoughts/questions I had along the way
Just on trailing newlines.... there's a few files where it is missing which I find quite irksome! Especially when you do something like below, and end up with the command prompt printing on the same line as the file content. admin@alpine:~/Powerwall-Dashboard$ cat compose.env.sample
# Environment variables for docker compose.
#
# GRAFANAUSER - may need to be adjusted for cases such as rootless docker.
# See issue #22,
# https://github.com/jasonacox/Powerwall-Dashboard/issues/22#issuecomment-1253076441)
GRAFANAUSER="1000:1000"admin@alpine:~/Powerwall-Dashboard$ I just went through all the files and identified the below with missing trailing newlines:
I would recommend adding the trailing newline to those files. There are more without the trailing newline, but those are .json files so I have ignored them since they shouldn't have the trailing newline? Some do have a trailing newline however so it is a bit inconsistent, but probably doesn't matter too much with those. |
This comment was marked as resolved.
This comment was marked as resolved.
Something like renaming |
This comment was marked as resolved.
This comment was marked as resolved.
ok, I think we're close. once you're happy with the changes: lmk and I'll rebase these 16 down to like, 4 commits or something something sane for the overall commit history. |
Wow! @YesThatAllen this looks great. Thank you!! 🙇 I can squash and merge unless you think it is better to keep it as ~4 commits. @mcbirse thanks for your review as well. |
Nah, squashing to master as one commit is fine. I just didn't want 16 commits in master lol. |
.editorconfig
Outdated
indent_size = 2 | ||
indent_style = space |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasonacox / @mcbirse I'm just assuming 2 spaces vs tabs is your preference.
Not every file matches this setting.
The editorconfig does NOT force changes, but does attempt to tell the editor how it should behave when you're adding new code.
Please make sure this is your preference before squashing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a mix, but 4 spaces is my preference (as seen in most of the *py, *sh and *yml) but I know we have 2 spaces in *conf.
Yes, I know, we aren't consistent. This should help. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
.editorconfig
Outdated
# 4 space indentation | ||
[*.py] | ||
indent_size = 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the default for the repo is 4 spaces, we can remove this fallout.
Not needed since default is already 4 spaces.
Merged! I'll test and set this up as v2.9.5. Testing
|
@YesThatAllen - Thank you! 🙏 |
Less goooo |
Repo cleanup ref: #265