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

Flatten editor directory #739

Merged
merged 1 commit into from
May 9, 2017
Merged

Flatten editor directory #739

merged 1 commit into from
May 9, 2017

Conversation

aduth
Copy link
Member

@aduth aduth commented May 9, 2017

Previously: #716, #736
Related: #737

This pull request expands upon the restructuring outlined in #716, eliminating an editor-specific components directory in favor of flattening the components into the top-level editor directory.

Open questions:

  • Do we want to flatten modes into the top-level directory as well?

Testing instructions:

Ensure the build completes, tests pass, and editor initializes and appears without regressions. Specifically observe that editable text regions retain appearance and behavior.

@aduth aduth added the Framework Issues related to broader framework topics, especially as it relates to javascript label May 9, 2017
@mtias
Copy link
Member

mtias commented May 9, 2017

I can see us doing /editor/visual-mode but it any case this looks good to me as is.

@mtias mtias self-requested a review May 9, 2017 19:08
@aduth aduth merged commit ac15682 into master May 9, 2017
@aduth aduth deleted the update/flatten-editor-directory branch May 9, 2017 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants