Added theme support and handling of utf-8 characters #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Successor of #23, solves #22 & #24 & (#20 & #26)
#22 Background Theme
@boyko-ant, I've updated it so that the user's selected theme is now used in the background of the widget.
#24 Non-ASCII character handling
I also updated to handling wiki pages with UTF-8 characters which were based on the changes made by Mikael Ekelund in his fork: stratiteq@e34430e.
However, the change did not work as all the encoding was done after the
" "to"+", which meant that all spaces got replaced by%2Binstead of+as per DevOps implementation. This PR is confirmed to now also work for UTF-8 characters, such as Ü.#20 & #26 Flickering widget when typing
Due to having a listener on
onFieldChanged, means that whenever any field on the work item, the widget gets reloaded, which creates the undeliverable flickering, that listener is now removed and no longer flickers when typing in any text field.Other remarks
Also updated categories as
Plan and trackis not a valid category anymore.Once these fixes as been pushed, I would highly recommend that @stratiteq and I (@BlackPhlox) take down our own published extensions of our forks, or at least make a deprecation notice, referencing the original extension as so to prevent confusion for other DevOps users.
Regarding the issue of linking to multiple wikis (#25), it should probably be documented in the description of the extension, that this is a limitation of DevOps and you have to link from the wiki page to work-item instead as shown by this comment: #25 (comment)