Skip to main content

3 New Code Cleanups from Dart Editor

Dart Editor has added three new code clean ups to its growing list:
  • Replace some methods with getters
  • Renaming some types
  • Removing abstract keyword for methods without a body

Other new features include:
  • New “Organize Imports” action
  • New migration Clean Ups -  replacing some methods with getters; renaming some types; removing “abstract” keyword for methods without body.
  • Enhanced “Extract Method” refactoring to allow changing parameter types
  • In the command-line debugger, we added the ability to pause a running isolate.
  • Improved how we display null value objects in the debugger.
  • Updated samples based on language and pub changes
  • Fixes for inline method and local
  • Fixes for syntax highlighting
  • Fix to automatically refresh out-of-sync resources
  • Fixes to better handle package symlinks in search and the files view.
And as always, view the changelog for the full list of changes, and to get started with the Editor see our tutorial.

The editor auto-updates now, so you should have these new features when you restart. You can check by opening Preferences and displaying Updates.

As always, the Dart encourages you to join the conversation on the Dart mailing list, ask questions on Stack Overflow, and file feature requests and bugs on dartbug.com.

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and Рeven more so Рfrom large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …