Project Information
- Repository: https://github.com/busyorg/busy
- Project Name: Busy
I reported the issue on the github.
Expected behavior
- A new reply should refresh automatically after writing it.
- An edited reply should refresh automatically.
These worked well before on Busy, and Steemit.com still works well.
Actual behavior
- A new reply cannot be shown without manual refresh.
- An edited reply doesn't refresh automatically.
Thus, it's impossible to distinguish whether a reply is actually written or not (or edited or not), and many users may write the same reply multiple times, or need to refresh the page manually.
How to reproduce
Currently, the issue happens all the time.
- For a new reply
- Write any reply.
- Then, the newly written reply doesn't show up unless you refresh manually.
- For an edited reply
- Edit any reply.
- Edited body doesn't refresh automatically.
- Browser version: Any
- App version: Busy 2.5.6 (current)
- Operating system: Any
Recording Of The Bug
writing a new reply
after submitting it, the new reply doesn't show up! So, it's impossible to know whether it's actually written or not.
need manual refresh to see the new reply, which was automatically shown before.
Cause
This is due to the deprecated API get_state explained here:
If any apps are still relying on get_state, we highly recommend ceasing use as soon as possible.
@steemitdev/upcoming-changes-to-api-steemit-com
Busy is using get_state to refresh the comment here:
