codex-team / codex-team/editor.js
Some great improvements
- Lingua principale
- TypeScript
- Stelle
- 31.9k
- Fork
- 2.2k
- Merge medio
- 1g 13h
- PR unite (30g)
- 2
Descrizione
I love this editor a lot. I love it some much that I can't express. I try to understand this editor code and do some improvement. It was very much difficult for me to understand all these code. So, I'm opening this issue to give some suggestions based on my experience which will make this editor great.
# Suggestion
- 1.Send number value corresponding to each type of data i.e paragraph, header, list, image etc.
This idea is inspired from *Medium*. They send number value instead of paragraph , list header etc. This will decrease data sharing between client and server. If we parse `paragrah` to paragraph tag or if we do this some arbitrary number, it's same.
If you will make this feature as an option then that will be also great. So, when we want data as text or number, we can decide and get that.
- 2.Sharing partial data when required
In medium I also noticed one feature that they share partial data( let's understand this by an example).
Example: we wrote an article we saved that, after sometime we again went to the article and we added one line to the end of the article then medium will only send one line of data with the line number. I am not saying you do exactly same but we can give both the data. Developer will decide which data they want to send.
- It also doesn't have great support for libraries and framework ( React, vue and angular)
**If this feature will be in core of editor then it will be really great.**
These are just suggestions, which can make it one of the greatest editor in the world. I'm also js developer I'm ready to work with all these features. I can't work alone because I don't know how this project work and I will need lots of time to understand the complete editor.
Thanks
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Non vengono indicati file, test o punti di ingresso. L’issue combina tipi di blocco numerici, condivisione di dati parziali e supporto per React/Vue/Angular; separa prima questi aspetti in proposte con ambito definito, quindi stabilisci un design condiviso e i criteri di accettazione per la funzionalità selezionata.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, react, typescript
- Ambito
- frontend
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 20/100