-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
feat(extensions/console): left align table entries #11295
Conversation
Co-authored-by: Jesse Jackson <jsejcksn@users.noreply.github.com>
Co-authored-by: Jesse Jackson <jsejcksn@users.noreply.github.com>
Co-authored-by: Simon Rask <SimonRask@users.noreply.github.com>
Thanks for the review @SimonRask and @jsejcksn. I've added both as co-authors. |
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.
Thank you!
Oh shit - I didn't maintain the co-author attributes for @SimonRask and @jsejcksn. I'm very sorry! Thank you for your contribution! |
@ry No problem — I'm just glad it was merged. It makes me wonder though:
|
Not really. When we merge something GitHub helpfully generates the co-author headers, but it is up to the commiter to remember to not delete them. While we could use something outside of GitHub to do the squash merge commits it likely would only cause other problems and make the workflow more complex. |
@kitsonk Thanks for responding. While the process wasn't exactly explained, it sounds like this is being done manually by the committer in a browser using the GitHub web UI.
There are many configurable GitHub bots available to help with this task. While it would necessarily add a bit of complexity, it would help by making the commit process more deterministic and implementing a desired procedure (e.g. enforcing conventional commit syntax, trimming out all of the granular commit history messages while maintaining co-authors, etc.). |
Fixes denoland#11295. The values of a column are left aligned if and only if the column contains at least one non-numerical value. ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ``` ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ```
Fixes denoland#11295. The values of a column are left aligned if and only if the column contains at least one non-numerical value. ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ``` ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ```
Fixes denoland#11295. The values of a column are left aligned if and only if the column contains at least one non-numerical value. Before ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ``` After ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ```
Fixes denoland#11295. The values of a column are left aligned if and only if the column contains at least one non-numerical value. Before ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ``` After ``` ┌───────┬───────────┐ │ (idx) │ Values │ ├───────┼───────────┤ │ 0 │ "apples" │ │ 1 │ "oranges" │ │ 2 │ "bananas" │ └───────┴───────────┘ ```
Fixes #11294
Before:
After:
(example taken from linked issue)