As mentioned by the other poster, it can sometimes be a little finicky in getting a new extension "kickstarted" in the MPOS solution. The full rebuild (as opposed to just "Build") is sometimes useful, as is right-clicking on "Pos.App" project and doing a manual deploy.
Also, make sure that the modulePath in the manifest.json is set to the name of your FILENAME (without the .ts extension) and not the name of the class. For instance, if I have a TriggerHandlers\PostSuspendTransactionTrigger.ts with a class named "MyPostSuspendTransactionTrigger":
export default class MyPostSuspendTransactionTrigger extends Triggers.PostSuspendTransactionTrigger {
... then my manifest.json file should look like this:
"triggers": [
{
"triggerType": "PostSuspendTransaction",
"modulePath": "TriggerHandlers/PostSuspendTransactionTrigger"
}
This is what you have in your post, so it should work. [Note that it's best practice to just name the file the same as the class.]
Finally, make sure that you add the URL of your manifest.json to the extensions.json file at the root of the Extensions subfolder:
{
"baseUrl": "PostSuspendTrigger"
}
That should be all you need to do to get your trigger to load and your breakpoint to be hit.
