fix: notification error navigate

[zhixzhan]

Description

Task Item

closes #2533
closes #2546

Screenshots

[cwhitten]

@zhixzhan why in the scenario of an inline LG error on a template like bdfactivity-23orinfe does the navigation take you to the all-up page? I thought the intention was to navigate to the action directly in this case of inline LG or LU errors. Was this behavior changed by design?

[zhixzhan]

@cwhitten By design it should navigate to inline, current not working come from 2 reason.

1. after involved projectId &locale the url calculation did not been updated (fixed now)
2. for some scenario of inline LU error ( maybe also LG in lower chance), our reverse calculate error's dialogPath rely on luParser can parse the error intent, so the error can be located in one intent, then the dialog use that this intent can be located, and calculate to a dialog path.

for 2 in conclusion, currently, not every inline error can be navigate back to inline editor because of our lg/lu Parser ability.

[cwhitten]

@cwhitten By design it should navigate to inline, current not working come from 2 reason.

1. after involved projectId &locale the url calculation did not been updated (fixed now)

I just tried it out and didn't see any different in behavior with a LG error. It still navigated to the all-up page

[zhixzhan]

@cwhitten By design it should navigate to inline, current not working come from 2 reason.

1. after involved projectId &locale the url calculation did not been updated (fixed now)

I just tried it out and didn't see any different in behavior with a LG error. It still navigated to the all-up page

can you paste the error lg file or bot, let me check again. if a LG error ( like just updated screenshot ) it did navigate to form editor

[zhixzhan]

@cwhitten updated, found another reason is lgNamePattern not updated from 'bdfactivity-233534' to 'bdfactivity-23orinfe'

[cwhitten]

nice!