initialize 0.6.0+1
initialize: ^0.6.0+1 copied to clipboard
Generic building blocks for doing static initialization.
0.6.0+1 #
- Fix for
LibraryIdentifierpaths when initializer starts from inline scripts inside of subfolders.
0.6.0 #
- Added the
fromoption torun. This should be aUripointing to a library in the mirror system, and throws if not in mirrors mode. This can be used to run initializers in a custom order at development time. - This package no longer tries to handle initializing scripts found in html
imports. If you need this feature please use
initWebComponentsfrom theweb_componentspackage.
0.5.1+8 #
- Make sure to crawl the entire supertype chain for annotations, and run them in reverse order.
0.5.1+7 #
- Change to source order-crawling of directives instead of alphabetical. The one
exception is for
partdirectives, those are still crawled in alphabetical order since we can't currently get the original source order from the mirror system.
0.5.1+6 #
- Fix some analyzer warnings.
0.5.1+4 #
- Update to use mock dart sdk from
code_transformersand update theanalyzerandcode_transformersdependencies.
0.5.1+3 #
- Fix up mirror based import crawling so it detects dartium and only crawl all libraries in the mirror system in that case.
0.5.1+2 #
- Fix handling of exported libraries. Specifically, annotations on exported libraries will now be reached and imports in exported libraries will now be reached.
- Add support for scripts living in html imports without adding an html dependency by crawling all libraries in the mirror system in reverse order, instead of just the root one.
0.5.1+1 #
- Make sure to always use
path.urlin the transformer.
0.5.1 #
- Added support for more types of expressions in constructor annotations. More
specifically, any const expressions that evaluate to a
String,int,double, orboolare now allowed. The evaluated value is what will be inlined in the bootstrap file in this case.
0.5.0 #
- The
InitializePluginTransformeris gone in favor of a newInitializerPluginclass which you can pass a list of to theInitializeTransformer. These plugins now have access to the fully resolved ast nodes and can directly control what is output in the bootstrap file.
0.4.0 #
Lots of transformer updates:
- The
new_entry_pointoption is gone. The bootstrapped file will now always just be the original name but.dartwill be replaced with.initialize.dart. - The
html_entry_pointoption is gone, and the file extension is now used to detect if it is an html or dart file. You should no longer list the dart file contained in the html file. Effectively resolves 13. - The
entry_pointoption has been renamedentry_pointsand now accepts either a single file path or list of file paths. Additionally, it now supports Glob syntax so many files can be selected at once. Resolves 19.
0.3.1 #
- Added
InitializePluginTransformerclass inplugin_transformer.dartwhich provides a base transformer class which can be extended to perform custom transformations for annotations. These transformers should be included after the maininitializetransformer and work by parsing the bootstrap file so the program doesn't need to be re-analyzed.
0.3.0 #
- Library initializers now pass a
LibraryIdentifiertoinitializeinstead of just aSymbol. This provides the package and path to the library in addition to the symbol so that paths can be normalized.
0.2.0 #
-
entryPointandnewEntryPointtransformer options were renamed toentry_pointandnew_entry_pont. -
Added
html_entry_pointoption to the transformer. This will search that file for any script tag whose src isentry_pointand rewrite it to point at the bootstrapped filenew_entry_point. -
Top level properties and static class properties are now supported in initializer constructors, as well as List and Map literals, 5.
0.1.0+1 #
Quick fix for the transformer on windows.