Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Q quickfix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • quickfixgo
  • quickfix
  • Merge requests
  • !357

Add top of tag stack to error on repeating groups

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open blutack requested to merge github/fork/blutack/feature/improve_repeating_group_errors into main 6 years ago
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 1

Sorry about the last one, forgot to do the pull against a branch.

Currently, debugging an incorrect repeating group template which is missing a tag is difficult because the required information (i.e. the tag which caused quickfix to think it had reached the end of the group) is not surfaced anywhere.

Adding the top tag of the stack to the error message makes debugging these issues much simpler. If tv[0] can be null, this might be problematic and a different solution will be needed!

Activity

  • Loading
  • Loading
Please register or sign in to reply

There are currently no pipelines.

To run a merge request pipeline, the jobs in the CI/CD configuration file must be configured to run in merge request pipelines.

0 Assignees
None
Assign to
0 Reviewers
None
Request review from
Labels
0
None
0
None
    Assign labels
  • Manage project labels

Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Lock merge request
Unlocked
2
2 participants
Administrator
blutack
Reference: quickfixgo/quickfix!357
Source branch: github/fork/blutack/feature/improve_repeating_group_errors

Menu

Explore Projects Groups Snippets