-
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
fix: block component block not available yet #745
Conversation
d303046
to
94098df
Compare
@@ -16,7 +16,7 @@ const { title, id, description, attestationsCreated, tags } = | |||
<li class=`${containerStyles.container} container`> | |||
<h2> | |||
<a href={generatePath(paths.ctypeDetails, id)} class="title"> | |||
{title} | |||
{title.length > 0 ? title : '∅'} |
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.
It’s unclear to me whether this is still needed, but okay. This could also be spelled simpler by the way.
{title.length > 0 ? title : '∅'} | |
{title || '∅'} |
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 thought ""
was truthty, but you are right it is falsy, so that's possible.
During a regression test after ctypehub/pull/743, it was found that the "Registration Block" component was showing a broken link after creating a cType from inside the app. This was because the block was still not available and the link required the block number.
Now:
When submitting a cType creation transaction, it will be awaited until it is InBlock.Other fix:
Handle cTypes without a title.