source_span is a library for tracking locations in source code. It's designed
to provide a standard representation for source code locations and spans so that
disparate packages can easily pass them among one another, and to make it easy
to generate human-friendly messages associated with a given piece of code.
The most commonly-used class is the package's namesake,
represents a span of characters in some source file, and is often attached to an
object that has been parsed to indicate where it was parsed from. It provides
access to the text of the span via
SourceSpan.text and can be used to produce
human-friendly messages using
When parsing code from a file,
SourceFile is useful. Not only does it provide
an efficient means of computing line and column numbers,
FileSpans that are able to provide more context for their
FileSpan.highlight()now properly highlights point spans at the beginning of lines.
FileSpan.highlight()would put the highlight indicator in the wrong position when highlighting a point span after the end of a file.
SourceFile.span() now goes to the end of the file by default, rather than
ending one character before the end of the file. This matches the documented
FileSpan.context now includes the full line on which the span appears for
empty spans at the beginning and end of lines.
Fix an edge case where
FileSpan.highlight() could crash when highlighting a
span that ended with an empty line.
Produce better source span highlights for multi-line spans that cover the entire last line of the span, including the newline.
Produce better source span highlights for spans that contain Windows-style newlines.
Improve the output of
<3.0.0, and adjust other dependencies.
new SourceFile() constructor is deprecated. This constructed a source
file from a string's runes, rather than its code units, which runs counter to
the way Dart handles strings otherwise. The
constructor (see below) should be used instead.
new SourceFile.fromString() constructor was added. This works like
SourceFile(), except it uses code units rather than runes.
The current behavior when characters larger than
0xFFFF are passed to
SourceFile.decoded() is now considered deprecated.
SourceSpan.highlight(), which returns just the highlighted text that would be included in
SourceSpanWithContext.contextto be overridden in strong mode.
FileSpan.end. In 1.2.0 these were mistakenly changed from
SourceLocation directly is deprecated. Instead,
extend the new
SourceLocationBase class or mix in the new
Dramatically improve the performance of
SourceFilewhen repeatedly called.
FileSpan.unioncould throw an exception for external implementations of
==, but not
no longer throw exceptions for external implementations of
FileSpan.hashCode now fully agrees with
SourceSpanWithContextto allow multiple occurrences of
FileSpan's context to include the full span text, not just the first line of it.
SourceSpanWithContext: a span that also includes the full line of text that contains the span.
Avoid unintentionally allocating extra objects for internal
SourceSpan.operator== works on arbitrary
This package was extracted from the
source_maps package, but the
API has many differences. Among them:
Span has been renamed to
Location has been renamed to
SourceLocation to clarify their purpose and maintain consistency with the
package name. Likewise,
SpanException is now
SpanFormatException is not
FixedLocation have been rolled into the
Location classes, respectively.
SourceFile is more aggressive about validating its arguments. Out-of-bounds
lines, columns, and offsets will now throw errors rather than be silently
Uri objects rather than
Strings. The constructors allow either
SourceFile.getLocationMessage are now
SourceFile.message, respectively. Rather than
taking both a
useColor and a
color parameter, they now take a single
color parameter that controls both whether and which color is used.
Span.isIdentifier has been removed. This property doesn't make sense outside
of a source map context.
SourceFileSegment has been removed. This class wasn't widely used and was
inconsistent in its choice of which parameters were considered relative and
Add this to your package's pubspec.yaml file:
dependencies: source_span: ^1.5.4
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
flutter packages get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|1.5.4||Jan 29, 2019|
|1.5.3||Jan 24, 2019|
|1.5.2||Jan 17, 2019|
|1.5.1||Jan 14, 2019|
|1.5.0||Jan 10, 2019|
|1.4.1||Jul 18, 2018|
|1.4.0||May 17, 2017|
|1.3.1||Jan 7, 2017|
|1.3.0||Nov 8, 2016|
|1.2.4||Oct 21, 2016|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Feb 20, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter, web, other
No platform restriction found in primary library
lib/src/span_mixin.dart. (-0.50 points)
lib/src/span_mixin.dart reported 1 hint:
line 54 col 9: Use
isNotEmpty for Iterables and Maps.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
source_span.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
The package description is too short. (-7 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.