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

chore(ui): organise component directory structure #15199

Merged
merged 4 commits into from
Feb 16, 2024

Conversation

chirag-madlani
Copy link
Collaborator

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@github-actions github-actions bot added UI UI specific issues e2e:Lineage safe to test Add this label to run secure Github workflows on PRs labels Feb 15, 2024
Copy link
Contributor

github-actions bot commented Feb 15, 2024

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 61%
61.53% (31409/51047) 40.5% (12516/30900) 40.87% (3859/9441)

Copy link

@chirag-madlani chirag-madlani merged commit 146ccc5 into main Feb 16, 2024
16 of 18 checks passed
@chirag-madlani chirag-madlani deleted the restruc-component branch February 16, 2024 04:53
Copy link
Contributor

@ShaileshParmar11 ShaileshParmar11 left a comment

Choose a reason for hiding this comment

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

left few comments

Copy link
Contributor

Choose a reason for hiding this comment

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

We should name the parent folder as DataInsight instead of DataInsightDetail, following same naming convention as other folder

Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest we should keep one folder for TestSuites instead of 2 folder (TestSuite & TestSuites)

Copy link
Contributor

Choose a reason for hiding this comment

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

TableProfiler folder should be part of Profiler, also some files are lying without the folders

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Files without folder will leave for individual to update I just reorg them to their parent folder for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e:Lineage e2e This will trigger e2e test workflows safe to test Add this label to run secure Github workflows on PRs UI UI specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants