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

(CAT-1167) Fix failing legacy fact autocorrector #138

Merged
merged 2 commits into from
Jul 28, 2023

Conversation

LukasAud
Copy link

@LukasAud LukasAud commented Jul 27, 2023

Prior to this commit, attempting to autocorrect a legacy fact would output the wrong result. This happened due to a conflict between the actions of the legacy fact plugin and the interference of the top scope fact plugin.

This commit aims to prevent the top scope fact plugin from attempting to correct any legacy fact by whitelisting all legacy keywords. Legacy fact plugin already performs the work of the top scope fact plugin so no functionality should be lost.

This should fix #106 and close #114

Checklist

  • 🟢 Spec tests.
  • 🟢 Acceptance tests.
  • Manually verified.

@LukasAud LukasAud added the bug Something isn't working label Jul 27, 2023
@LukasAud LukasAud requested review from a team and bastelfreak as code owners July 27, 2023 09:18
Copy link
Collaborator

@bastelfreak bastelfreak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome fix. does it make sense to add tests for the legacy facts to ensure they are still fixed correctly?

@bastelfreak
Copy link
Collaborator

git says the file is now marked executeable. Was that on purpose?

@LukasAud
Copy link
Author

LukasAud commented Jul 27, 2023

Removing some unnecessary tests and implementing another one to keep check on the new behaviour. Unit tests for legacy and top scope plugins should be plenty enough here tbh.

Also, I dont think I intended to make it executable. Must have assigned it 755 at some point by mistake.

Prior to this commit, attempting to autocorrect a legacy fact would
output the wrong result. This happened due to a conflict between the
actions of the legacy fact plugin and the interference of the top
scope fact plugin.

This commit aims to prevent the top scope fact plugin from
attempting to correct any legacy fact by whitelisting all legacy
keywords. Legacy fact plugin already performs the work of the top scope
fact plugin so no functionality should be lost.
@LukasAud LukasAud force-pushed the bugfix-legacy_fact_corrector branch from cb26a5b to bea0e5a Compare July 27, 2023 10:45
@LukasAud LukasAud closed this Jul 27, 2023
@LukasAud LukasAud reopened this Jul 27, 2023
@LukasAud LukasAud changed the title (Bugfix) Fix failing legacy fact autocorrector (CAT-1167) Fix failing legacy fact autocorrector Jul 27, 2023
@GSPatton GSPatton merged commit 03bb0ea into main Jul 28, 2023
10 checks passed
@GSPatton GSPatton deleted the bugfix-legacy_fact_corrector branch July 28, 2023 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Top scope facts not being extracted correctly
3 participants