|
| 1 | +<!--suppress HtmlRequiredTitleElement --> |
| 2 | +<html lang="en"> |
| 3 | + <head> |
| 4 | + <style> |
| 5 | + code, pre { |
| 6 | + font-family: monospace; |
| 7 | + } |
| 8 | + |
| 9 | + h1 { |
| 10 | + font-size: 1.2em; |
| 11 | + margin-bottom: 5px; |
| 12 | + } |
| 13 | + |
| 14 | + #table-of-contents h2 { |
| 15 | + font-size: 1em; |
| 16 | + font-weight: normal; |
| 17 | + margin: 0 0 5px 0; |
| 18 | + } |
| 19 | + |
| 20 | + #table-of-contents p { |
| 21 | + font-size: 0.96em; |
| 22 | + margin: 0 0 0 9px; |
| 23 | + } |
| 24 | + |
| 25 | + #contributors h2 { |
| 26 | + margin-top: 20px; |
| 27 | + margin-bottom: 0; |
| 28 | + } |
| 29 | + </style> |
| 30 | + </head> |
| 31 | + <div id="table-of-contents"> |
| 32 | + <h2>Table of contents:</h2> |
| 33 | + <p>• Apologies</p> |
| 34 | + <p>• Compatibility with IDEA 2022.*</p> |
| 35 | + <p>• Fixes in 0.20.1</p> |
| 36 | + <p>• Quick Documentation issues (Platform)</p> |
| 37 | + </div> |
| 38 | + <h1>Apologies</h1> |
| 39 | + <p> |
| 40 | + Many of you probably asked themselves why I haven't been updating this plugin as frequently as I did in the past. |
| 41 | + </p> |
| 42 | + <p> |
| 43 | + Well, long story short, I haven't been working on IDEA - at least not constantly - |
| 44 | + as I've been developing Eclipse RCP products and plugins starting from April 2021, with a development stack |
| 45 | + that isn't what you'd look for nowadays. The products' VCS, Rational Team Concert, isn't supported |
| 46 | + at all in IDEA (I did open a ticket for IBM in 2018), so that ruled out completely the possibility of using it. |
| 47 | + </p> |
| 48 | + <p> |
| 49 | + Other than that, I was burned-out and just thinking about committing to GitHub made me really uncomfortable. |
| 50 | + I kept postponing forever in favor of playing Call of Duty (gotta admit that). Maybe I was feeling a bit down, |
| 51 | + or maybe I was stressed out too much. |
| 52 | + <br/> |
| 53 | + I hope this shed some light on what was going on during these last months, and it's indeed my fault |
| 54 | + if I haven't answered issues or pull requests. |
| 55 | + </p> |
| 56 | + <p> |
| 57 | + Some of you emailed me directly, and I really appreciated it. My email (<code>lp.edoardo@gmail.com</code>) is always open, |
| 58 | + so if you notice I'm not answering on GitHub, you're welcome to forward your issues there too! |
| 59 | + <br/> |
| 60 | + I'd like to thank everyone who still visited the repository to report issues or to try to fix what I wasn't able to fix |
| 61 | + myself. |
| 62 | + </p> |
| 63 | + <h1>Compatibility with IDEA 2022.*</h1> |
| 64 | + <p> |
| 65 | + The biggest change that comes with this release is compatibility with IDEA 2022.*. As I was mentioning in |
| 66 | + previous <i>What's new</i> pages, my goal is to keep supporting as many Platform's versions as possible, |
| 67 | + so that people with older IDEs are still able to enjoy using Conventional Commits. |
| 68 | + </p> |
| 69 | + <p> |
| 70 | + Unfortunately, each new version increases the odds of unexpected behaviors, which can obviously |
| 71 | + only be observed at runtime. For your interest, I'm using a special annotation, |
| 72 | + <a href="https://github.com/lppedd/idea-conventional-commit/blob/master/src/main/kotlin/com/github/lppedd/cc/annotation/Compatibility.kt">@Compatibility</a>, |
| 73 | + to document code that is written for the specific purpose of supporting every possible version. |
| 74 | + <br/> |
| 75 | + Have a look at its usages if you want. |
| 76 | + </p> |
| 77 | + <h1>Fixes in 0.20.1</h1> |
| 78 | + <p>This minor release fixes a couple of issues, specifically:</p> |
| 79 | + <ul> |
| 80 | + <li> |
| 81 | + <a href="https://github.com/lppedd/idea-conventional-commit/issues/70">Issue #70</a><br/> |
| 82 | + Using the tab key inside the commit panel was producing an exception since, probably, the latest 2021.3 versions. |
| 83 | + Why? Well, the commit's text editor needs to handle the tab key differently from all the other text editors |
| 84 | + (e.g. to easily navigate the <i>scope</i> token), so a custom handler is injected. That handler was in fact trying |
| 85 | + to do something which would result in a deadlock, and the Platform was stopping it before it would happen. |
| 86 | + </li> |
| 87 | + <li> |
| 88 | + <a href="https://github.com/lppedd/idea-conventional-commit/issues/64">Issue #64</a><br/> |
| 89 | + Sometimes the VCS token provider would try to access a deleted repository root. |
| 90 | + Why? As you may know, direct modifications to the file system are not immediately reflected inside IDEA, |
| 91 | + and that means a non-existent repository root might be still valid for the IDE. |
| 92 | + </li> |
| 93 | + </ul> |
| 94 | + <h1>Quick Documentation issues (Platform)</h1> |
| 95 | + <p> |
| 96 | + The Quick Documentation component seems to not be stable anymore since the beginning of 2021. |
| 97 | + We currently have an <a href="https://github.com/lppedd/idea-conventional-commit/issues/57">issue</a> opened for this, |
| 98 | + but beware this is in fact a Platform problem. |
| 99 | + </p> |
| 100 | + <p> |
| 101 | + Here are the relevant issues on IDEA's YouTrack:<br/> |
| 102 | + <a href="https://youtrack.jetbrains.com/issue/IDEA-261691">IDEA-261691</a><br/> |
| 103 | + <a href="https://youtrack.jetbrains.com/issue/IDEA-262653">IDEA-262653</a><br/> |
| 104 | + <a href="https://youtrack.jetbrains.com/issue/IDEA-292730">IDEA-292730</a> |
| 105 | + </p> |
| 106 | +</html> |
0 commit comments