-
Notifications
You must be signed in to change notification settings - Fork 2
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
Reduction in line character limit #48
Comments
hi! thank you for this thoughtful issue! i'm sorry that the long line limits are an accessibility issue for you, and i certainly agree that 200 is quite a bit too long for readability. i'd suggest moving back toward the 80 character limit in one complication is that Bixby's main purpose is to insulate adopters from the frequent style changes once(?) included in i'd be happy to spearhead this for |
Hello @no-reply, Thank you for responding to me. I realise that this is a rather subjective issue, much like tabs vs. spaces. So might I suggest that, inline with the Ruby Style guide you mentioned above, that 120 characters is a compromise between the very long 200 characters lines and the a 1990s terminal width of 80 characters, whilst airing on the side of readability and increased comprehension.
Thank you again for getting back to me and taking this issue so seriously. |
@prdanelli that seems about right. i think my personal practice for some years now has been a soft limit at 80, and a very hard limit at 120. we should probably give it a bit for others to chime in, but in the meanwhile let's start thinking about how we can facilitate a gradual cleanup over at hyrax and hyku, at least. |
This sounds like a potential developers congress issue both discussion and cleanup. |
I have been working within the Hyku codespace for a little while and have been struggling with the higher character limit that you permit for each line of code - I believe this is currently set to 200 characters per line.
As someone who struggles periodically due to mild dyslexia, incredibly long lines of code are far harder to comprehend in their entirety than those which have been broken up for brevity.
I will provide an example below and please note I mean no disrespect to the owner of this code, it is only used because of its length of 184 characters - 16 character below your upper limit:
If this were broken up so that the options for the
build_for
method were on a seperate line, the entire condition can be much more easily comprehended:Thank you.
The text was updated successfully, but these errors were encountered: