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

feat(MIG-166): throw manifest not found error #500

Merged
merged 3 commits into from
Jan 15, 2024

Conversation

abulseed
Copy link
Contributor

Follow up PR to resolve an issue with the error code that is thrown if there is no manifest file provided to the import command.

@@ -34,6 +34,10 @@ class StudyDataTranslations {
}
}

if (!manifestData) {
throw Fault.create('mdctl.kManifestNotFound.error', { reason: 'There is no manifest set as parameter neither found in directory' })
Copy link
Contributor

Choose a reason for hiding this comment

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

The error message seems ambiguous to me, what about this?
No manifest found in the parameters and in the import directory

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sounds the same to me

Copy link
Collaborator

@joejean joejean Jan 10, 2024

Choose a reason for hiding this comment

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

I guess the grammatically correct version should be "There is no manifest set as a parameter, nor is one found in the directory."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@imaimai86 @joejean just updated the error message as u guys suggested.

@alahawash
Copy link
Collaborator

Hi @abulseed we've released 1.0.71, can you branch out of it?

@abulseed
Copy link
Contributor Author

abulseed commented Jan 11, 2024

@alahawash it seems that the changes related to MIG-166 doesn't exist on 1.0.71. Did we create this branch from 1.0.70?

@alahawash
Copy link
Collaborator

@alahawash it seems that the changes related to MIG-166 doesn't exist on 1.0.71. Did we create this branch from 1.0.70?

Ohh that's awful, we've got to reconcile those branches. Can this MR wait?

@abulseed
Copy link
Contributor Author

@alahawash it seems that the changes related to MIG-166 doesn't exist on 1.0.71. Did we create this branch from 1.0.70?

Ohh that's awful, we've got to reconcile those branches. Can this MR wait?

yes no worries this can wait. Sounds good please let me know.

@alahawash
Copy link
Collaborator

Hi @abulseed , please rebase from main which should include all changes from 1.0.70 and 1.0.71. Going forward we'll be using main as our trunk

@abulseed abulseed changed the base branch from release/1.0.70 to main January 15, 2024 13:12
@abulseed abulseed force-pushed the feature/MIG-166_followup branch 2 times, most recently from 8dc76d1 to 5a0aa4e Compare January 15, 2024 13:22
@abulseed
Copy link
Contributor Author

@alahawash just rebased from main would u please review it now? i tried to minimize the changes appearing on this PR but failed to get the changes needed for MIG-166.

are we sure we have merged 1.0.70 into main? i have searched on main for this file packages/mdctl-axon-tools/lib/StudyDataTranslations.js but couldn't find it.

@alahawash
Copy link
Collaborator

You are right @abulseed , when I merged before my local wasn't up-to-date. I did merge again and you should not have any issues now if you rebase from main. Sorry for the that

@abulseed
Copy link
Contributor Author

@alahawash done! please review..

Copy link
Collaborator

@alahawash alahawash left a comment

Choose a reason for hiding this comment

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

LGTM

@abulseed abulseed merged commit 282bc18 into main Jan 15, 2024
@abulseed abulseed deleted the feature/MIG-166_followup branch January 15, 2024 15:30
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.

4 participants