Skip to content

Conversation

@seancolsen
Copy link
Contributor

@seancolsen seancolsen commented Dec 5, 2025

Fixes #4921

Related

Checklist

  • My pull request has a descriptive title (not a vague title like Update index.md).
  • My pull request targets the develop branch of the repository
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added tests for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Comment on lines +173 to +182
const { apiContext } = this;
function* getApiRequests() {
for (const [columnId, displayOptions] of changes.entries()) {
yield api.columns.metadata.set({
...apiContext,
column_meta_data_list: [{ attnum: columnId, ...displayOptions }],
});
}
}
await batchRun([...getApiRequests()]);
Copy link
Member

Choose a reason for hiding this comment

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

I'll say this, I like generators, however I find .map(...) more readable for usages like these.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, that's fair. Thinking back on this code, I think at some point I had been using some more logic inside that function, and then that changed. I don't recall exactly. I agree that in this case array mapping would be cleaner and more readable.

Copy link
Member

@pavish pavish left a comment

Choose a reason for hiding this comment

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

@seancolsen This works really well!

I added 58ce552 to exit early from columnsDatastore.setDisplayOptions when there are no entries, because batchRun (and batchSend) throw an error when there are no requests. This scenario happens when the user changes the width of a joined column.

The error from batchRun doesn't cause any problem, however, we ought to either remove that error or make the types more strict to avoid any uncaught exceptions.

@pavish pavish added this pull request to the merge queue Dec 10, 2025
Merged via the queue into develop with commit 71c5958 Dec 10, 2025
22 checks passed
@pavish pavish deleted the 4921_resize_columns branch December 10, 2025 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-status: review A PR awaiting review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow resizing multiple columns at once

3 participants