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

Fix settings persistence: we save IDs, thus we should parse IDs inste… #1116

Merged

Conversation

Vassiliy-Kudryashov
Copy link
Member

…ad of display names

Description

The issue appears after recent display name changes (JUnit4 -> JUnit 4 etc.)

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual Scenario

Start IDE, try generation. Exception appears.

Checklist (remove irrelevant options):

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • No new warnings

@Vassiliy-Kudryashov Vassiliy-Kudryashov merged commit dc586fa into main Oct 7, 2022
@Vassiliy-Kudryashov Vassiliy-Kudryashov deleted the Vassiliy-Kudryashov/fix_settings_persistence branch October 7, 2022 14:45
@alisevych alisevych added this to the 2022.10.1 Release milestone Oct 10, 2022
AbdullinAM pushed a commit to AbdullinAM/UTBotJava that referenced this pull request Oct 17, 2022
UnitTestBot#1116)

Fix settings persistence: we save IDs, thus we should parse IDs instead of display names
AbdullinAM pushed a commit to AbdullinAM/UTBotJava that referenced this pull request Oct 17, 2022
UnitTestBot#1116)

Fix settings persistence: we save IDs, thus we should parse IDs instead of display names
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants