-
Notifications
You must be signed in to change notification settings - Fork 1
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
Syncing workspace and code #51
base: staging
Are you sure you want to change the base?
Conversation
ee4f7d3
to
8a17258
Compare
c93a71a
to
8e35af1
Compare
Modify sidebar
…componets-structure Building meta components from its default code
Modification of custom page
Performance improvement
Fixed the routing issue in netlify
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.
would recomend rambda, instead of lodash
this.plugin = declare(() => { | ||
return { | ||
visitor: { | ||
ArrowFunctionExpression: (path: any) => { |
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.
what if the component is not a arrow function but rather a normal es5 function?
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 thik you can use the alias Function
} | ||
if (childrenProp) { | ||
dispatch.components.unexpose('children') | ||
|
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.
This clickhandler is doing way too many things. and logic which needs a seperate reducer itself.
And every time a key is pressed this handler is being redefined
if (visitedComponentName === componentName) { | ||
const attribute = toJsxAttribute('isContainerComponent', 'true') | ||
|
||
openingElement.attributes.push(attribute) |
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.
why are we pushing this attribute?
|
||
const index = openingElement.attributes.findIndex( | ||
(attribute: any) => attribute.name.name === 'isCustomComponent', | ||
) |
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.
better way to remove an attribute is to use .filter and filter it out.
import useDispatch from '../../../hooks/useDispatch' | ||
import UnExposePropButton from '../../actionButtons/UnExposePropButton' | ||
import CustomPropDeletionButton from '../../actionButtons/CustomPropDeletionButton' | ||
import { checkIsCustomPage } from '../../../core/selectors/page' |
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.
The logic in this component is way more than what a FormControl component needs to do.
For example: this component acts differently if the form control is representing the props of a Custom Component, or the props a child components of a custom component which are exposed.
Ideally this should have been two different components itself
Testing and improving App perfomance
Improving the perfomance of the app
No description provided.