Skip to content

Conversation

@rimildeyjsr
Copy link
Contributor

@rimildeyjsr rimildeyjsr commented Aug 15, 2020

Description

Motivation & context

Flatten the directory structure of fast components and fast-foundation elements:

  1. change structure of /accordion/accordion-item -> /accordian and /accordian-item
  2. change structure of /progress/progress and /progress/progress-ring -> /progress and /progress-ring
  3. change structure of /tabs/tab and /tabs/tab-panel -> /tabs, /tab and /tab-panel

Fixes #3641

Issue type checklist

  • Chore: A change that does not impact distributed packages.
  • Bug fix: A change that fixes an issue, link to the issue above.
  • New feature: A change that adds functionality.

Is this a breaking change?

  • This change causes current functionality to break.

Adding or modifying component(s) in @microsoft/fast-components checklist

Process & policy checklist

  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

@ghost
Copy link

ghost commented Aug 15, 2020

CLA assistant check
All CLA requirements met.

@EisenbergEffect EisenbergEffect added this to the Release 08 milestone Aug 17, 2020
@janechu
Copy link
Collaborator

janechu commented Aug 17, 2020

Looks like you need to update the pathing in the *.stories.ts files, you can try running storybook locally in fast-components and checking to make sure things are looking correct that way as well.

@rimildeyjsr
Copy link
Contributor Author

@janechu thanks for the pointer! will do that 😄

@rimildeyjsr rimildeyjsr force-pushed the master branch 3 times, most recently from 7b74014 to 9150fb1 Compare August 19, 2020 00:09
@rimildeyjsr rimildeyjsr changed the title chore: flatten directory for accordian, progress, tabs in fast-compon… chore: flatten directory for accordian, progress, tabs in fast-components and fast-foundation Aug 19, 2020
@rimildeyjsr rimildeyjsr changed the title chore: flatten directory for accordian, progress, tabs in fast-components and fast-foundation chore: flatten directory structure for fast-components and fast-foundation Aug 19, 2020
@rimildeyjsr rimildeyjsr changed the title chore: flatten directory structure for fast-components and fast-foundation chore: change directory structure for fast-components and fast-foundation Aug 19, 2020
@rimildeyjsr rimildeyjsr changed the title chore: change directory structure for fast-components and fast-foundation chore: change directory structure for components Aug 19, 2020
@rimildeyjsr
Copy link
Contributor Author

@janechu - Verified the changes on local, everything seems to be working fine now! I just can't get this lint_title build to succeed :(

@nicholasrice
Copy link
Contributor

@rimildeyjsr Don't worry about lint_title ;) That fails for all PRs coming from a fork for unknown reasons.

@rimildeyjsr
Copy link
Contributor Author

@nicholasrice ah ok! 😅

Comment on lines +20 to +21
export * from "../tab";
export * from "../tab-panel";
Copy link
Member

Choose a reason for hiding this comment

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

I know these were previously being exported from this file, but now that we've gone to a flat structure, does this still make sense? I would expect that we might just export these from their own folders and export them directly from the root.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense, will make the changes

Copy link
Member

Choose a reason for hiding this comment

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

@rimildeyjsr it looks like this didn't fully get implemented from what I see but I think that's ok. I'm worried about this going too stale, so I've made an update here and if it passes the build I'll likely merge this and we can address this in a follow-up.

Comment on lines 2 to 3
export * from "./progress.template";
export * from "../progress-ring/index";
Copy link
Member

Choose a reason for hiding this comment

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

Same question here as with tabs:

I know these were previously being exported from this file, but now that we've gone to a flat structure, does this still make sense? I would expect that we might just export these from their own folders and export them directly from the root.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense, will make the edit!

Comment on lines 3 to 4
export * from "../tab/index";
export * from "../tab-panel/index";
Copy link
Member

Choose a reason for hiding this comment

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

should these be exported from their own index file rather than this one now that we've gone to a flat structure?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

They are being exported from their own index file, this was an unnecessary reference. Removing it

export * from "./accordion.template";
export * from "./accordion";
export * from "./accordion-item";
export * from "../accordion-item";
Copy link
Member

Choose a reason for hiding this comment

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

Should this be exported from it's own index file?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

accordion item is being exported from its own index file, this export is not required. Removing.

@rimildeyjsr
Copy link
Contributor Author

@chrisdholt - have made the changes as you suggested!

@rimildeyjsr rimildeyjsr force-pushed the master branch 2 times, most recently from c1b32fb to a4bf41e Compare August 21, 2020 18:05
@EisenbergEffect
Copy link
Contributor

@awentzel Can you take a look into what's happening with CI here? It's been running the unit test task for almost an hour. All this PR does is move files and fix up paths.

@awentzel
Copy link
Collaborator

I'm investigating the CI issue...

@awentzel
Copy link
Collaborator

awentzel commented Sep 2, 2020

A GH Support Ticket has been filed to address this as I was unable to resolve. https://support.github.com/ticket/personal/0/821492

I'm hopeful that there are additional diagnostics from GH team to help resolve. As a possible workaround, I have considered merging without the testing successfully passing, then test after it's in master. However, I wanted to give GH a chance to respond first. This was marketed as high importance so hopefully, they come back soon.

@awentzel awentzel modified the milestones: Release 10, Release 12 Sep 2, 2020
@awentzel awentzel closed this Sep 3, 2020
@awentzel awentzel reopened this Sep 3, 2020
@chrisdholt
Copy link
Member

Pulling this down to test locally - I'd like to get this in so we don't get too out of sync and run into conflicts with changes to currently nested files.

@chrisdholt
Copy link
Member

chrisdholt commented Sep 11, 2020

I think I have this fixed - I'm going to add and commit the changes.

@chrisdholt chrisdholt merged commit 6be7114 into microsoft:master Sep 11, 2020
@chrisdholt
Copy link
Member

Thank you for the contribution @rimildeyjsr - and thanks for hanging with us while we debugged the build issue! 🎉

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.

Flatten the folder structure of components

6 participants