The Student Room Group

Have a list on what is planned on being imported to react from ST2

Scroll to see replies

Original post by DFranklin
To put my "dev" hat on for a minute:

Realistically, a list of what's fixes/missing functionality is coming to React almost certainly doesn't exist (and "can't exist").

There will be a list of tickets with things like "Support TSR Smileys", "Provide Multiquote Functionality", "Support the {noparse} tag". Someone will assign priorities, and (in general) things get worked on according to their priority.

There will be some tickets assigned a "won't fix" priority - typically things where the "bug" is actually intended behaviour, or "we know fixing this would cause a bunch of other problems / be an insane amount of work".

But the normal way things "don't get fixed" is just that they are never high enough priority to get dealt with. They're on the system, TSR would like them to be fixed. But it just never actually happens.

The problem is that the priority system usually isn't accurate enough for even something vague like "the P1 stuff will happen, the P2 stuff might happen, the P3 stuff won't happen". I'm sure the original plan was (along the lines of) "When we deploy React, it will have multi-quote, images, bbcode edit mode". And then deadlines approached and a bunch of "must happen" stuff became "we'll do it later (maybe)". And conversely, something can be low priority and a developer has a thought "you know, I bet we could do that by doing XYZ", spends half an hour looking at it, and then it's done and ready for the next release.

Looking at what's been fixed (or hasn't) over the last two months, I expect an awful lot of missing functionality is going to fall in that "it's on the list, we have no idea when we'll get around to it" dead-zone.


I personally do not need or want a date (other community members might feel differently), just a list of what is coming or what’s not regardless of priority: https://docs.google.com/spreadsheets/d/1-VBsO9c3oSUzTs_S7eLKLyhLIOELjxMGsEd2DYdbwPU

I’ve attached a Spreadsheet for people to see what I’m talking about (and what I mean when I created this thread).
I would have thought the project plan for a major rebuild like this to include some indication of what functionality was planned to be replicated and what was being retired.

It might not be as detailed as “this list of BBCodes” or “these emojis” but a review of the current functionality and what would be in scope for rebuilding seems like a fairly standard starting point.

It might be that some of the lost functionality that has been raised since launch was missing from the plans or that the issues with page loading speed have bumped things down or off the list but I would be very worried if there wasn’t something plotting out the baseline before anyone started writing code.
Something as simple as this then if people want specific dates on when functionality X is coming then that’s a different matter entirely but that’s not what I expect.

I mean sure you can give dates if you want though.
Original post by Talkative Toad
I personally do not need or want a date (other community members might feel differently), just a list of what is coming or what’s not regardless of priority: https://docs.google.com/spreadsheets/d/1-VBsO9c3oSUzTs_S7eLKLyhLIOELjxMGsEd2DYdbwPU

I’ve attached a Spreadsheet for people to see what I’m talking about (and what I mean when I created this thread).

What I'm saying is that without a timescale (or priority), I suspect there will be virtually nothing on the list that is "definitely not coming to React".

Everywhere I've ever worked, there's a huge number of tickets where we haven't said "we're not going to do this", but internally it's not a priority and it's very unlikely to happen. Something more important always has to be done first.

Clearly TSR is suffering heavily from "stuff that has to be done first", so I'd expect it to be much the same.
I would have thought the project plan for a major rebuild like this to include some indication of what functionality was planned to be replicated and what was being retired.

It might not be as detailed as “this list of BBCodes” or “these emojis” but a review of the current functionality and what would be in scope for rebuilding seems like a fairly standard starting point.

It might be that some of the lost functionality that has been raised since launch was missing from the plans or that the issues with page loading speed have bumped things down or off the list but I would be very worried if there wasn’t something plotting out the baseline before anyone started writing code.

I mean like MR, I just had the assumption that all the current functionality was going to be imported and that there might or could be a chance to update some of it (e.g improve the functionality of the ignore list system for example as things are coming off of VBulletin so now is the perfect time to improve/rework it imo).

But my assumption appears to be incorrect based on the reading I’ve done with regards to the update and people being told to make threads in the give feedback or report a problem forum for any functionality that they want (even if said functionality is simply basic functionality that exists in ST2):
https://www.thestudentroom.co.uk/showpost.php?p=99051315&postcount=9
https://www.thestudentroom.co.uk/showpost.php?p=99051315&postcount=10
https://www.thestudentroom.co.uk/showpost.php?p=99051315&postcount=11

So hence me creating this thread as I can see that a lot of users (from all spectrums, not just established/power house users) are frustrated by the lack of functionality on React and the clarity surrounding the communication or you’re getting (newer) users ask “how do I search in a thread?”, “where are TSR emojis?”, “How do I upload an image?”.

In my case I’m simply making threads to report bugs or to ask for missing functionality back or I’m saying that full functionality should have been built into React before releasing it to the masses whilst simultaneously giving most users no opt out of the update.

I’ve said this at least twice in the thread already but I believe that it could be less headache for most parties if users were just given a list on what plans on coming to React from ST2 and what doesn’t that way we know what functionality to request for and to make informed decisions on whether we need to change the way we use TSR or if we want to quit all together as a result. Even if no dates or timeline is given.

If my assumption (that all ST2 functionality was going to be imported to React) isn’t incorrect then please (someone who has more insight into this) tell people this or prove it.
(edited 9 months ago)
Original post by DFranklin
What I'm saying is that without a timescale (or priority), I suspect there will be virtually nothing on the list that is "definitely not coming to React".

Everywhere I've ever worked, there's a huge number of tickets where we haven't said "we're not going to do this", but internally it's not a priority and it's very unlikely to happen. Something more important always has to be done first.

Clearly TSR is suffering heavily from "stuff that has to be done first", so I'd expect it to be much the same.

You’re probably right.
Will the permission/functionality where Ex-VT+/Current VT+ and Ex-subscribers (people part of the subscriber group that therefore gives them the ability to change their username colour although I’m not sure if this permission applies to them) don’t see Ads on TSR be imported from ST2 to React or not?

It’s a simple yes or no question.

I currently don’t see Ads on ST2 regardless of whether I have Adblock on or not.

But on React I see Ads if my Adblock is not switch on.

On the App I see Ads (well not at the moment for some reason) and there’s no way for me to turn them off (but I quite like seeing ads on the app and I like the way that they appear).
(edited 8 months ago)
I’ll bump this in hopes that this actually happens soon or for me to be told that it won’t *actually* happen.

Quick Reply