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

FIO-9176: fix component path in error info #170

Closed
wants to merge 2 commits into from

Conversation

Maria-Golomb
Copy link
Contributor

@Maria-Golomb Maria-Golomb commented Oct 15, 2024

Link to Jira Ticket

https://formio.atlassian.net/browse/FIO-9176

Description

Removed path override in scope.error for components without parent. This allows to get full path to components inside components such as edit grid and avoid an error when there are components with same key inside and outside edit grid component.

Dependencies

formio/formio.js#5867

How has this PR been tested?

autotests
manually

Checklist:

  • I have completed the above PR template
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • My changes include tests that prove my fix is effective (or that my feature works as intended)
  • New and existing unit/integration tests pass locally with my changes
  • Any dependent changes have corresponding PRs that are listed above

Comment on lines 154 to 156
if(component.parent){
cleanedError.context.path = absolutePath;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the behavior when the component is not in a parent? Is there a test for that case?

Comment on lines +176 to 179
if (component.parent) {
cleanedError.context.path = absolutePath;
}
cleanedError.context.path = absolutePath;
Copy link
Contributor

Choose a reason for hiding this comment

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

This change doesn't make sense to me. It seems to me that the path field will always be absolute path. What am I missing?

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.

2 participants