-
Notifications
You must be signed in to change notification settings - Fork 611
chore: change directory structure for components #3730
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
Conversation
|
Looks like you need to update the pathing in the |
|
@janechu thanks for the pointer! will do that 😄 |
7b74014 to
9150fb1
Compare
|
@janechu - Verified the changes on local, everything seems to be working fine now! I just can't get this |
|
@rimildeyjsr Don't worry about lint_title ;) That fails for all PRs coming from a fork for unknown reasons. |
|
@nicholasrice ah ok! 😅 |
| export * from "../tab"; | ||
| export * from "../tab-panel"; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
| export * from "./progress.template"; | ||
| export * from "../progress-ring/index"; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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!
| export * from "../tab/index"; | ||
| export * from "../tab-panel/index"; |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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"; |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
|
@chrisdholt - have made the changes as you suggested! |
c1b32fb to
a4bf41e
Compare
|
@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. |
|
I'm investigating the CI issue... |
|
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. |
|
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. |
|
I think I have this fixed - I'm going to add and commit the changes. |
|
Thank you for the contribution @rimildeyjsr - and thanks for hanging with us while we debugged the build issue! 🎉 |
Description
Motivation & context
Flatten the directory structure of fast components and fast-foundation elements:
Fixes #3641
Issue type checklist
Is this a breaking change?
Adding or modifying component(s) in
@microsoft/fast-componentschecklistProcess & policy checklist