-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-13266] Import from LogMeOnce not working 2.0 #11452
base: main
Are you sure you want to change the base?
Conversation
Thank you for your contribution! We've added this to our internal Community PR board for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dlfi Thank you for your contribution.
The changes look pretty straightforward, but I was wondering, if you'd be up to adding some unit-tests to verify old and new behaviour.
Examples can be found under the libs/importer/spec
-folder. There are a couple of csv-file-importers that have tests which you can use as guidance.
Thank you for approval for workflows @djsmith85 and I would be happy to do tests! Already thought about it. I will try as soon as possible. Should it be in this pull request or do I need to make a new issue for tests? |
@dlfi Tests should be added with this PR, then we can verify everything in one place before passing it on to QA. |
Hi @djsmith85 I just added the tests to PR. I hope I did it right, I was inspired by the tests you linked me to. Sorry it took so long. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work on adding the test cases @dlfi. Just some minor changes and then this ready to get passed on to QA.
Thanks again for your contribution!
import { data as logmeonceData2 } from "./test-data/logmeonce-csv/logmeonce.test.invalidRow.csv"; | ||
import { data as logmeonceData6 } from "./test-data/logmeonce-csv/logmeonce.test.invalidUrl.csv"; | ||
import { data as logmeonceData5 } from "./test-data/logmeonce-csv/logmeonce.test.missingName.csv"; | ||
import { data as logmeonceData4 } from "./test-data/logmeonce-csv/logmeonce.test.mixedData.csv"; | ||
import { data as logmeonceData3 } from "./test-data/logmeonce-csv/logmeonce.test.multipleEntries.csv"; | ||
import { data as logmeonceData } from "./test-data/logmeonce-csv/logmeonce.test.validData.csv"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of re-naming the exports, could you please use meaningful names for the exported members within the testdata-files. You can then just import them here and won't need to rename.
Something like:
import { invalidRowData } from "./test-data/logmeonce-csv/logmeonce.test.invalidRow.csv";
import { missingNameData } from "./test-data/logmeonce-csv/logmeonce.test.missingName.csv";
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For sure! Thank you for the comment I just changed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick changes. Approving and moving this to QA for testing.
Once they give their okay, this can get merged and will be included in a future release.
New Issues
Fixed Issues
|
Fixes #11406
🎟️ Tracking
📔 Objective
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes