-
Notifications
You must be signed in to change notification settings - Fork 8
feat(typesync): update to latest dep versions. use new hypergraph types #202
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
….whited/feat-typesync-hypergraph-updates
….whited/feat-typesync-hypergraph-updates
….whited/feat-typesync-hypergraph-updates
…ucture. fix create app call
@cmwhited is attempting to deploy a commit to the The Graph Foundation team on Vercel, but is not a member of this team. To resolve this issue, you can:
To read more about collaboration on Vercel, click here. |
typeIdx={props.typeIndex} | ||
typePropertyIdx={idx} | ||
value={thisType?.properties?.[idx]?.typeName || 'Text'} | ||
value={thisType?.properties?.[idx]?.type_name || 'Text'} |
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 guess we need snake case here for some reason. Some API? Just curious if there is something we can change so you don't need snake case.
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 is the name of the property in the database. I initially had a new type for the form, that I was mapping back and forth between, but decided that felt confusing and redundant so just used the db type. but this will change in my next PR to work through form issues and restructure components
Description
effect
, etc. and many of the deps within thetypesync
)Type
from@graphprotocol/hypergraph