Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change all parsers from KotlinInquirer to Kotter #3610

Open
1 of 14 tasks
Nereboss opened this issue May 7, 2024 · 1 comment
Open
1 of 14 tasks

Change all parsers from KotlinInquirer to Kotter #3610

Nereboss opened this issue May 7, 2024 · 1 comment
Labels
blocked The issue or feature is blocked on another issue or PR that has to be resolved first pr-analysis Issues that touch the analysis pr(oject). tech For technical stories without user impact (=refactoring stories).

Comments

@Nereboss
Copy link
Contributor

Nereboss commented May 7, 2024

Feature request

In #3609 we rebuilt the functionality of KotlinInquirer with Kotter and integrated it into the StructureModifier.
As each parser requires refactoring of its parserDialog, as well as all tests (tests previously used mocking that we plan to remove), each parser should be handled in a separate PR.

Here is a list of all parsers that need to be adjusted:

  • merge
  • Edge filter
  • Modify (structure modifier)
  • Csvimport
  • Sonarimport
  • Sourcemonitorimport
  • svnlogparser
  • gitlogparser
  • csvexport
  • sourcecodeparser
  • codemaatimport
  • tokeiimporter
  • rawtextparser
  • metricgardenerimport

Description

As a developer, I want each parser to be handled separately so that each has a smaller separate PR instead of one very big one for all parsers.

Acceptance criteria

Assumptions & Exclusions

Development notes (optional Task Breakdown)

  • [ ]
  • [ ]
  • [ ]

Open questions

@Nereboss Nereboss added pr-analysis Issues that touch the analysis pr(oject). tech For technical stories without user impact (=refactoring stories). blocked The issue or feature is blocked on another issue or PR that has to be resolved first labels May 7, 2024
@Nereboss
Copy link
Contributor Author

Nereboss commented May 7, 2024

This is blocked until #3609 is finished

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked The issue or feature is blocked on another issue or PR that has to be resolved first pr-analysis Issues that touch the analysis pr(oject). tech For technical stories without user impact (=refactoring stories).
Projects
None yet
Development

No branches or pull requests

1 participant