Request to add edit UI for one single record
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
You can use this template for reporting bugs.
Feel free to remove parts that are not relevant, or just write something free-form if you prefer.
What did you do?
- I double clicked on a DB row from the table view
What did you expect to happen?
- I expected to see a UI to edit this single row as I used to see from PG Commander:
What actually happened?
- I could only edit the value of my clicked cell.
- When the value is long, I could not see the full content since the text box is not resizable.
What software versions are you using?
Postico version:
Version 1.5.20 (8940)
macOS version:
12.2.1 (21D62)
PostgreSQL version:
PostgreSQL 14.2 on aarch64-apple-darwin21.3.0, compiled by Apple clang version 13.0.0 (clang-1300.0.29.30), 64-bit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by locating the table view and its single-cell editing behavior, then determine how a full-row editor should fit there; done means double-clicking a row opens an editable UI for the record and long values can be viewed fully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, postgresql
- Domain
- database, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100