Nested quotes
-
@jarey well, I gave you a solution to hide them if you want. There is also already a built-in feature to hide deeply nested quotes with a little arrow button to show them.
-
@PitaJ said in Nested quotes:
@jarey well, I gave you a solution to hide them if you want. There is also already a built-in feature to hide deeply nested quotes with a little arrow button to show them.
Css solutions are nice but can be considered as a patch only.
You already used mention instead of quote on this topic and you said that people using long nestquotes are doint it wrong, then why have that option? Only for that people?Also nodebb is not only webapplication, hiding with css will only work for website but you will still get full quotes with hundreds of > characters on pushbullet,telegram,rss,email etc
Just to be clear. I dont want nested quote to be removed but a good solution could be to have the option to enable/disable on admin panel or avoid to nest quotes till infinite, maybe 4-5 max.
Thanks for the replies
-
@exodo hour about this: we modify the "quote" feature (clicking quote beneath a post) and make it so it automatically removes the extra quotes before they are even added to the composer.
-
@PitaJ said in Nested quotes:
4 deep
3 deep
2 deep
1 deep
0
To hide nested quotes 3 deep or more, you can use the following custom CSS:
blockquote > blockquote blockquote { display: none; }To hide 2 deep or more, use this:
blockquote blockquote { display: none; }Also, what happened to the quote collapsing? It works on this forum.
This workaround is shit. It is inefficient. It could reach a high data usage over 3G/4G. As you said, users dont need more than 3 levels of deep, so why not to remove it? We could do NodeBB easier, faster and more efficient.
-
Why not remove it?
Because it's an intrinsic part of markdown that requires work to remove.
-
@PitaJ said in Nested quotes:
@exodo hour about this: we modify the "quote" feature (clicking quote beneath a post) and make it so it automatically removes the extra quotes before they are even added to the composer.
sorry for my english but i didnt undertand this sentence, can you explain?
-
@exodo there's a quote feature. The "quote" link below the post automatically copies the text from the quoted post and inserts quotes in front. If, instead, we parse out those nested quotes when the text is copied, they will be removed before the post is even submitted.
For instance: if we have a post like this
The sky is blue
The grass is green
Then the "quote" reply post in the composer would be like this normally (before the reply was written):
> > The sky is blue > > The grass is greenBut instead the nested quotes are removed like so:
> The grass is green -
@PitaJ said in Nested quotes:
@exodo there's a quote feature. The "quote" link below the post automatically copies the text from the quoted post and inserts quotes in front. If, instead, we parse out those nested quotes when the text is copied, they will be removed before the post is even submitted.
For instance: if we have a post like this
The sky is blue
The grass is green
Then the "quote" reply post in the composer would be like this normally (before the reply was written):
> > The sky is blue > > The grass is greenBut instead the nested quotes are removed like so:
> The grass is greenSeems ok as long as it works.
we had modified composer just for that time ago but i prefer suggest new additio s amd changes for community before modify core or core plugins. -
@PitaJ said in Nested quotes:
Why not remove it?
Because it's an intrinsic part of markdown that requires work to remove.
we only need a simple regex, we did it in older versions with a custom composer (https://github.com/exo-do/nodebb-plugin-composer-exodo/commit/da2351cf94baf1c8580af4c760b1ff19785e3198), but we cannot maintain our own custom composer. It should be part of default NodeBB composer.
