Atom 1.37 has shipped! This version introduces a complete flow for handling review comments you’ve received on a pull request and an experimental faster mode in fuzzy finder that dramatically improves its performance.
Pull request review comments in the GitHub package
Responding to review comments that a reviewer has left on a pull request you’ve submitted can be cumbersome. You need to cross-reference lines back and forth between GitHub and your editor, using the diff context and line numbers to find the place where the comment was made.
Now, to reduce the amount of mental context switching you need to do, we show reviews and review comments right in your favorite editor To open the all-new reviews tab, click on the “see reviews” button in the GitHub tab while you’re on a branch associated with a pull request, or click “see reviews” in the footer of a pull request detail view.
With the reviews tab open, expand any review comment thread to read how awesome your code is. Click “Jump To File” to open or focus an editor and scroll to that line, or click “open diff” to scroll to the commented line on the diff in the pull request detail view. We’ll automatically account for any changes you’ve made locally but haven’t pushed yet.
While you’re in an editor, any lines that have been commented on are highlighted. Click on the comment icon in the left gutter to jump back to that comment in the review tab.
Beneath the comment thread in the reviews tab, you can respond to the thread directly with the provided text box to keep the conversation going, or react with a reaction emoji. When you’re satisfied that you’ve addressed the feedback from a specific comment thread, click “Resolve conversation” to mark the thread as resolved. To help you keep track of your progress through review feedback, resolved comment threads will be greyed out and counted in a progress bar at the top of the tab.
Get the bar green, get those green checks, and get your code shipped!
Dramatic fuzzy-finder performance boost
Similarly, the filtering performance has been drastically improved. This means that results will show much faster while typing on the fuzzy finder.
These two improvements are most noticeable in projects with large numbers of files - for example, we measured a 14x speed boost in the crawling performance on a project with 270K files.
Since these changes cause some slightly different results, we’ve placed them behind a configuration option for now while we work out any unexpected kinks in the transition. When you open a project with a large amount of files you’ll see a prompt to enable it:
Authenticate and encrypt communications over Atom’s activation socket
While it’s launching, Atom uses a UNIX domain socket (on macOS and Linux) or a named pipe (on Windows) to determine if an existing main process is hanging around to open a window for you before starting a new one. Now, all communication that occurs through that channel is authenticated and encrypted to keep other people with access to your machine from reading or interfering with those messages.
As a related change, the
--socket-path command-line argument has been removed, although it doesn’t look like it was used outside of internal testing.
Language package improvements
The bundled language packages have another set of goodies in the pipeline in beta as well:
language-clojurecan handle non-ASCII characters in keywords, symbols, and identifiers, like the clojure compiler itself, thanks to @PEZ.
@caleb531 made the
language-pythontree-sitter grammar able to recognize shebang lines that reference “python2” or “python3” instead of just “python”.
language-tomlnow correctly tokenizes multiple key/value pairs on a single line, again thanks to @caleb531
language-rubyrecognizes “next” as a keyword thanks to @willcosgrove.
Don’t forget to check out all the other improvements shipping with Atom 1.37 in the release notes!
Atom 1.38 Beta
Atom 1.38 beta includes some improvements on the GitHub package and a few fixes on the language parsers.
Github package improvements
- Now Atom displays an “edited” label next to a pull request comment if it has been edited.
- User badges (like “First time contributor” or “Collaborator”) are shown next to the authors on PRs and review comments to encourage people to be kind to new folks.
- Resolved comments are grouped together to make the pull request conversation easier to read.
Fixes when handling some languages
A few fixes have been added to the language parsers/syntax highlighter. Now Atom allows folding the
default label in
switch statements, it improves the handling of comment characters in ERB and it fixes an issue when folding
if statements in Python.
Community Contribution Highlights
We’re thankful for the community contributors that help Atom get better on each release. These are some of them:
- Thanks @50Wliu for adding a way to move conflicting entries, this is a really nice improvement to the Tree View!
- Props to @brainsnail for adding support for Go module and checksum files in our language parser, now people can use new Go features in Atom and get proper highlighting.
There are many more details in the release notes.
Get all these improvements today by joining the Atom Beta Channel!