Multiple infobases with reused group names aren't handled correctly.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
When you have multiple infobases configured, and they use groups with the same names, they are not correctly disambiguated.
For example, if you have "Group A" in INFO1.FFF and another in INFO2.FFF, and a link in one of them defined as <QL:Query,"[Group 'Group A']",RH>, it could wind up resolved to either infobase.
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
Start by locating the infobase configuration and link-resolution entry points, then reproduce the example with INFO1.FFF and INFO2.FFF each containing a Group A. Confirm that a QL link to [Group 'Group A'] resolves to the group in the correct infobase, and add or run the relevant tests if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100