| commit | b47ec06848bf3e14de0e66bd21224b94fdfbada3 | [log] [tgz] |
|---|---|---|
| author | Adrià Vilanova Martínez <me@avm99963.com> | Sun Jan 15 17:43:26 2023 +0100 |
| committer | Adrià Vilanova Martínez <me@avm99963.com> | Sun Jan 15 18:19:22 2023 +0100 |
| tree | 5aa2694eeac1ab1589049ffa7a6cbc24906635ae | |
| parent | db38d7f281eb87247488cdd8ac423392c3536fbf [diff] |
Flatten threads: fix for application/json+protobuf responses When a new message is created in a thread, the thread itself is reloaded, but via an application/json+protobuf request (array-like data) instead of a regular text/plain request (object-like data). Since the code didn't work well for these types of requests, the thread didn't fully load. This CL fixes this issue by correctly handling application/json+protobuf responses in the response modifiers. An issue with the read-only interceptors has also been fixed, and tests have been added to ensure that the array-like to object-like and viceversa transformation functions work properly. Bug: twpowertools:153 Change-Id: If6cd5adc67d676bf36986f325e791124fa71da51
- .babelrc[Added - diff]
- .eslintrc.json[diff]
- Makefile[diff]
- jest.config.js[Added - diff]
- package-lock.json[diff]
- package.json[diff]
- src/common/protojs.js[diff]
- src/common/protojs.test.mjs[Added - diff]
- src/models/Message.js[diff]
- src/xhrInterceptor/XHRProxy.js[diff]
- src/xhrInterceptor/responseModifiers/flattenThread.js[diff]
- src/xhrInterceptor/responseModifiers/index.js[diff]
- src/xhrInterceptor/responseModifiers/loadMoreThread.js[diff]
- .github/
- cws/
- docs/
- playbooks/
- roles/
- src/
- templates/
- tools/
- .babelrc
- .clang-format
- .editorconfig
- .eslintrc.json
- .gitignore
- .gitreview
- .zuul.yaml
- i18n-config.toml
- jest.config.js
- LICENSE
- Makefile
- OWNERS
- package-lock.json
- package.json
- README.md
- tagRelease.bash
- webpack.config.js
TW Power Tools
An extension which brings several enhancements to the Google Forums and the Community Console.
For a list of features/enhancements, check out the feature list doc.
Information for contributors
This extension is being actively developed, and everyone is welcome to make feature requests, report issues and contribute code changes.
In order to make feature requests or report issues, please do so at the Monorail Issue Tracker:
To see a more exhaustive guide on how to contribute, and information on how to contribute code changes, please read the following doc:
Beta channel
Before releasing updates to the stable channel, the newest versions are uploaded to the beta channel so they can be tested by everyone who's interested. This is another way to contribute to the project, because beta testing can make us notice bugs before they reach the stable channel.
The beta channel for Chrome is available here.