Added autocomplete and image upload support to compose#77
Added autocomplete and image upload support to compose#77elliotBraem merged 6 commits intoNEARBuilders:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@Megha-Dev-19 Could this be configured to work with the existing Markdown editor? Was there any specific motivation to use SimpleMDE?
I think we could copy the pattern from mob.near/widget/MainPage.N.Compose.Common -- notice how this Common "wrapper" is able to take in a custom markdown editor (our current) from props, and then passes these functionalities to it. For context, the goal is that we can use these features in whatever editor we plan to swap it out for. The implementation should be style agnostic. Also see #83 and #82 |
|
hey @elliotBraem, the reason I moved to SimpleMDE, the current editor doesn't capture the change in text when it's done outside it's scope, so if I update the post (by using autocomplete), the state is updated but not visible in markdown, since it takes the state only in initial render, but now if I think about it I believe I can move certain things from SimpleMDE code to the existing one to make it work. |
|
@Megha-Dev-19 Ahhh I see, ya I think this is a similar issue @itexpert120 is running into for #81. If it's not too much work, I think it's worth the exploration. Ideally, we should be able to swap between the two editors (any editor) with no change in the behavior or extra configuration. Being able to update content would solve #78, too
On near.social, there's this special icon that gets clicked and shows the "advanced" markdown editor.
We can keep the editor as it is now, but I like the pattern in mob.near/widget/MainPage.N.Common.Compose; you can swap out whichever editor you use via a widgetSrc in props and it'll work the same |
|
@elliotBraem I have forked the |


Resolves #61