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

[PM-13266] Import from LogMeOnce not working 2.0 #11452

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

dlfi
Copy link

@dlfi dlfi commented Oct 7, 2024

Fixes #11406

🎟️ Tracking

📔 Objective

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 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

@dlfi dlfi requested a review from a team as a code owner October 7, 2024 22:34
@bitwarden-bot
Copy link

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-13266

@bitwarden-bot bitwarden-bot changed the title Import from LogMeOnce not working 2.0 [PM-13266] Import from LogMeOnce not working 2.0 Oct 7, 2024
Copy link
Contributor

@djsmith85 djsmith85 left a 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.

@dlfi
Copy link
Author

dlfi commented Oct 12, 2024

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?

@djsmith85
Copy link
Contributor

@dlfi Tests should be added with this PR, then we can verify everything in one place before passing it on to QA.

@dlfi
Copy link
Author

dlfi commented Oct 31, 2024

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.

@djsmith85 djsmith85 self-assigned this Oct 31, 2024
@djsmith85 djsmith85 self-requested a review November 5, 2024 18:41
Copy link
Contributor

@djsmith85 djsmith85 left a 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!

Comment on lines 4 to 9
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";
Copy link
Contributor

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";

Copy link
Author

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.

@dlfi dlfi requested a review from djsmith85 November 5, 2024 20:50
djsmith85
djsmith85 previously approved these changes Nov 5, 2024
Copy link
Contributor

@djsmith85 djsmith85 left a 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.

@djsmith85 djsmith85 added the needs-qa Marks a PR as requiring QA approval label Nov 5, 2024
Copy link
Contributor

github-actions bot commented Nov 5, 2024

Logo
Checkmarx One – Scan Summary & Details103e90a9-5ad9-4540-9819-bd8df4376c84

New Issues

Severity Issue Source File / Package Checkmarx Insight
MEDIUM Unpinned Actions Full Length Commit SHA /version-auto-bump.yml: 20 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 246 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 200 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 506 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 193 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 47 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 514 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 161 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /build-browser.yml: 366 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 186 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 179 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 498 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /build-browser.yml: 407 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 81 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 522 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 358 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /version-bump.yml: 296 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 246 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 47 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 193 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 81 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 296 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 179 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 522 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 506 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /build-browser.yml: 407 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 200 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 161 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 186 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 514 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 358 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /build-browser.yml: 366 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-auto-bump.yml: 20 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
LOW Unpinned Actions Full Length Commit SHA /version-bump.yml: 498 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Fixed Issues

Severity Issue Source File / Package
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 372
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 208
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 167
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 254
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 187
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 114
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 201
MEDIUM Unpinned Actions Full Length Commit SHA /build-browser.yml: 396
MEDIUM Unpinned Actions Full Length Commit SHA /version-auto-bump.yml: 40
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 306
MEDIUM Unpinned Actions Full Length Commit SHA /repository-management.yml: 194
MEDIUM Unpinned Actions Full Length Commit SHA /build-browser.yml: 355
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 254
LOW Unpinned Actions Full Length Commit SHA /build-browser.yml: 396
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 306
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 167
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 208
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 201
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 187
LOW Unpinned Actions Full Length Commit SHA /build-browser.yml: 355
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 372
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 114
LOW Unpinned Actions Full Length Commit SHA /repository-management.yml: 194
LOW Unpinned Actions Full Length Commit SHA /version-auto-bump.yml: 40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-pr needs-qa Marks a PR as requiring QA approval
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Import from LogMeOnce not working
3 participants