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

[Bug] unable to type email_verified_at #3624

Closed
Joso997 opened this issue Oct 5, 2023 · 6 comments
Closed

[Bug] unable to type email_verified_at #3624

Joso997 opened this issue Oct 5, 2023 · 6 comments

Comments

@Joso997
Copy link

Joso997 commented Oct 5, 2023

Bug Description

I am unable to write email_verified_at in a table. Copy Paste works though

How to Reproduce

Just start typing email_verified_at

Expected Behavior

it should be email_verified_at instead of email verified at

I can't reproduce it here in text, anyway like above where verified is italic without spaces between words.
I see this might be a problem here on GitHub too.

Operating System

Windows 10

AppFlowy Version(s)

0.3.4

Screenshots

No response

Additional Context

No response

@Joso997 Joso997 changed the title [Bug] [Bug] unable to type email_verified_at Oct 5, 2023
@MayurSMahajan
Copy link
Collaborator

Hey @Joso997! So you are not able to type things with _ (underscore) around them.
This is because wrapping words with an underscore is a markdown we use and also GitHub uses.
One way to get around it is by using a backslash like this:
\_sometext\_ this will show up like _sometext_ in Github

But now I have noticed that AppFlowy is not supporting the backslash key (). So that is a bug.
Thanks for bringing this to our attention.

@DevaanshPathak
Copy link

@MayurSMahajan I would like to work on this issue, please assign it to me. Thanks!

@MayurSMahajan
Copy link
Collaborator

MayurSMahajan commented Oct 7, 2023

@DevaanshPathak To solve this issue, you actually want to solve #3628.

@MayurSMahajan
Copy link
Collaborator

Oops I have already assigned #3628 to someone else, please look for other issues!

@DevaanshPathak
Copy link

Sure, Thanks @MayurSMahajan

@Xazin
Copy link
Contributor

Xazin commented Oct 25, 2023

Duplicate of #3628

@Xazin Xazin marked this as a duplicate of #3628 Oct 25, 2023
@Xazin Xazin closed this as completed Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants