Generated list pages resolve their relation label maps one lookup after another
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- performance
Research direction
Read loadLookups() in manage/list-page.js.template and list/page.js.template, then check how each lookup currently handles errors. The issue calls for independent lookups to run concurrently while preserving each lookup’s error handling. Done when labels appear after the slowest lookup rather than the sum of the round trips.
Written by the indexing model from the issue text.
Description
Issue
`loadLookups()` in the generated `manage/list-page.js.template` and `list/page.js.template` fetches the referenced rows of each relationship column one `await` at a time:
```js
const optCompany = await App.services.api.getAll('/.../CompanyController.java', { baseUrl: '' });
...
const optCurrency = await App.services.api.getAll('/.../CurrencyController.java', { baseUrl: '' });
```
The list itself does not wait for them (`loadLookups()` is not awaited), but every FK column shows its raw key until the LAST lookup of the chain has answered, so on a list with 8-10 relation columns the labels arrive after the sum of the round trips rather than the slowest one.
Found while fixing the same shape on the forms (#8344).
Expected
The lookups are independent and load concurrently (`Promise.all`, each keeping its own error handling), so the labels land after the slowest lookup, not after all of them in series.
- Dominant language
- Java
- Stars
- 278
- Forks
- 97
- Avg merge
- 15h 33m
- Merged PRs (30d)
- 301
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from eclipse-dirigible/dirigible
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-dirigible/dirigible#8636 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipse-dirigible/dirigible#8548 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipse-dirigible/dirigible#8240 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eclipse-dirigible/dirigible#8238 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eclipse-dirigible/dirigible#8232 ·
Maintainers usually reply within 1 day
All issues in eclipse-dirigible/dirigible
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
Area/Configuration Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ballerina-platform/static-code-analysis-tool#217 ·
Maintainers usually reply within 1 day
-
bug severity-medium XS
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nikolas-charalambidis/facepalm-maven-plugin#291 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
OakLoaf/PluginUpdater#264 ·
Maintainers usually reply within 1 day
-
[Bug]: withStartupTimeout() changes the startup timeout of all containers that use the default wait strategyPossibly taken @aymenjamaaoui claimed this today. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
testcontainers/testcontainers-java#12171 ·
Maintainers usually reply within 1 day