Skip to content

Commit c6ca2c8

Browse files
authored
Merge pull request #187 from oslabs-beta/master
Merging version 13.0
2 parents 2588ce8 + 5b6a112 commit c6ca2c8

File tree

82 files changed

+94374
-765
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

82 files changed

+94374
-765
lines changed

.travis.yml

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,17 @@
11
language: node_js
22
node_js:
3-
- "10"
4-
dist: trusty
3+
- "16"
4+
dist: xenial
5+
arch: amd64
6+
script:
7+
- python3 -VV
8+
- pip install --upgrade pip
9+
- pip -V
10+
- npm run test
511
cache:
612
directories:
713
- node_modules
814
install:
9-
- npm install
10-
- npm run prod-build
11-
script:
12-
- npm run test
13-
15+
- npm install --legacy-peer-deps
16+
env:
17+
global: PATH=/opt/python/3.7.1/bin:$PATH

CHANGE_LOG.md

Lines changed: 37 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,45 @@
33
<h1 align="center">ReacType Change Log</h1>
44
</p>
55

6+
**Version 13.0.0 Changes**
7+
8+
New Functionality:<br>
9+
- Manage state locally: Users can now manage state dynamically within nested components using React Hooks within the state manager tab.
10+
- Add/delete props: For a selected component, users can see a list of available props from the parent, add props, and delete props in case they are not - required later on.
11+
- State/props flow: If state or props are deleted upstream, it will automatically update the state for its children components.
12+
- Visualize state/props flow: Within the display sub-tab of the state manager tab, users can visualize an interactive tree diagram depicting the state initialized in the current component and passed down props from the parent component.
13+
14+
Enhancements:<br>
15+
- Live code preview: Live rendering of code based on any changes in the state and dragging and nesting of components.
16+
- Next.js & Gatsby compatibility: New state manager tab is now compatible with next.js and Gatsby.
17+
- Tutorial: Tutorial is functional and has the latest guides to navigate through the newly added state management tab.
18+
19+
Deployment Updates:<br>
20+
- Electron app is now available for Windows users.
21+
- Web based version of the app is available on Heroku.
22+
23+
Bug Fixes:<br>
24+
- User dashboard: The dashboard works now and shows private and shared projects with the ability for users to drop comments.
25+
- Login/logout: Users can now signup/login/logout now on both development and production environments.
26+
- Manage Projects: Github authenticated users are now able to create and save projects.
27+
- Customization: Use State works as expected now within HTML elements.
28+
29+
What’s next:<br>
30+
- Adding on click functionality within components. Goal: Make a fully functional tic-tac-toe app.
31+
- Incorporating material ui into the components so that exported app has visually appealing components.
32+
- Enabling auto save functionality when dragging and dropping components, and amending component state.
33+
- Allowing users to click and access projects within the dashboard for review.
34+
- Adding more integration and E2E testing.
35+
- Fixing bugs in the heroku (web based) deployment: login/logout, GitHub oauth etc.
36+
- Enabling google oauth in all environments.
37+
- Packaging electron app for Linux users.
38+
- Conversion from monolithic to micro services for better scaling in the future.
39+
640
**Version 12.0.0 Changes**
741

8-
-Context Visualizer: You can now visually see what component is consuming which context. As you click on the interactive tree, the component assigned to the context will be revealed.
9-
-React 18: Updated to React 18
10-
-Export Feature: Created an exportable context file, integrated with original codebase.
11-
Ready to go code: Added boilerplate codes to components based on which contexts they are consuming.
42+
- Context Visualizer: You can now visually see what component is consuming which context. As you click on the interactive tree, the component assigned to the context will be revealed.
43+
- React 18: Updated to React 18
44+
- Export Feature: Created an exportable context file, integrated with original codebase. Ready to go code: Added boilerplate codes to components based on which contexts they are consuming.
1245

1346
**A note to future contributors**
1447

Procfile

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
web: node server/server.js

README.md

Lines changed: 72 additions & 190 deletions
Large diffs are not rendered by default.

__tests__/BottomTabs.test.tsx

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,14 @@ function Test() {
1616
}
1717
test('Bottom Panel Contains Two Tabs: Code Preview and Component Tree', () => {
1818
render(<Test/>);
19-
expect(screen.getAllByRole('tab')).toHaveLength(2);
19+
expect(screen.getAllByRole('tab')).toHaveLength(7);
2020
expect(screen.getByText('Code Preview')).toBeInTheDocument();
2121
expect(screen.getByText('Component Tree')).toBeInTheDocument();
22+
expect(screen.getByText('Creation Panel')).toBeInTheDocument();
23+
expect(screen.getByText('Customization')).toBeInTheDocument();
24+
expect(screen.getByText('CSS Editor')).toBeInTheDocument();
25+
expect(screen.getByText('Code Preview')).toBeInTheDocument();
26+
expect(screen.getByText('Component Tree')).toBeInTheDocument();
27+
expect(screen.getByText('Context Manager')).toBeInTheDocument();
28+
expect(screen.getByText('State Manager')).toBeInTheDocument();
2229
})

__tests__/HTMLPanel.test.tsx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ function Test() {
1717
</DndProvider>
1818
)
1919
}
20-
test('Renders HTMLPanel component properly', () => {
20+
xtest('Renders HTMLPanel component properly', () => {
2121
render(
2222
<Test/>
2323
);
@@ -35,7 +35,7 @@ test('Renders HTMLPanel component properly', () => {
3535
expect(screen.queryByText('separator')).toBe(null);
3636
});
3737

38-
test('Adds new custom element', () => {
38+
xtest('Adds new custom element', () => {
3939
render(
4040
<Test/>
4141
);

0 commit comments

Comments
 (0)