OLD | NEW |
| (Empty) |
1 // Copyright (c) 2015, the Dart project authors. Please see the AUTHORS file | |
2 // for details. All rights reserved. Use of this source code is governed by a | |
3 // BSD-style license that can be found in the LICENSE file. | |
4 | |
5 /// Contains all error and warning messages produced by web_components. | |
6 library web_components.build.messages; | |
7 | |
8 import 'package:code_transformers/messages/messages.dart'; | |
9 | |
10 const scriptFileNotFound = const MessageTemplate( | |
11 const MessageId('web_components', 0), 'Script file at "%-url-%" not found.', | |
12 'URL to a script file might be incorrect', ''' | |
13 An error occurred trying to read a script tag on a given URL. This is often the | |
14 result of a broken URL in a `<script src="...">`. | |
15 '''); | |
16 | |
17 const scriptIncludedMoreThanOnce = const MessageTemplate( | |
18 const MessageId('web_components', 1), | |
19 'The `%-url-%` script was included more than once.', | |
20 'Dart script file included more than once.', ''' | |
21 Duplicate dart scripts often happen if you have multiple html imports that | |
22 include the same script. The simplest workaround for this is to move your dart | |
23 script to its own html file, and import that instead of the script (html imports | |
24 are automatically deduped). | |
25 | |
26 For example: | |
27 | |
28 <script type="application/dart" src="foo.dart"></script> | |
29 | |
30 Should turn into: | |
31 | |
32 <link rel="import" href="foo.html"> | |
33 | |
34 And `foo.html` should look like: | |
35 | |
36 <script type="application/dart" src="foo.dart"></script> | |
37 '''); | |
38 | |
39 const exactlyOneScriptPerEntryPoint = const MessageTemplate( | |
40 const MessageId('web_components', 2), | |
41 'Found either zero or multiple dart scripts in the entry point `%-url-%`. ' | |
42 'Exactly one was expected.', | |
43 'Each entry point html file should contain exactly one dart script tag.', | |
44 'Each entry point html file should contain exactly one dart script tag.'); | |
45 | |
46 const internalErrorDontKnowHowToImport = const MessageTemplate( | |
47 const MessageId('web_components', 3), | |
48 "internal error: don't know how to include %-target-% from" | |
49 " %-source-%.%-extra-%", "Internal error: don't know how to include a URL", | |
50 ''' | |
51 Sorry, you just ran into a bug in the web_components transformer code. Please | |
52 file a bug at <https://github.com/dart-lang/web-components/issues/new> | |
53 including, if possible, some example code that can help the team reproduce the | |
54 issue. | |
55 '''); | |
56 | |
57 const inlineImportFail = const MessageTemplate( | |
58 const MessageId('web_components', 4), | |
59 'Failed to inline HTML import: %-error-%', 'Error while inlining an import', | |
60 ''' | |
61 An error occurred while inlining an import in the web_components build. This is | |
62 often the result of a broken HTML import. | |
63 | |
64 One possible cause is using an @HtmlImport containing a relative path from | |
65 within an inline script tag, see http://goo.gl/ZgrhaV. The workaround currently | |
66 is to use a `package:` url instead, move the code to a dart file, or simply | |
67 adding a real html import (since you are already in an html file). | |
68 '''); | |
OLD | NEW |