Support arbitrary list properties #48
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #46.
ListPropertywhich can have any other property as its internal type. This required some less-pretty auto-naming of internally declared enums/objects (now suffixing "item") to support arbitrarily nested lists.propertyandsourceargument.propertyis the actual property being called,sourceis where the value for that property is coming from. This allows calling property constructors from within other property constructors and eliminates hard codingdictsyntax.get_importsfunction on every property. This can handle both relative and absolute imports. Removes the need to check property type before adding imports at higher levels and allows lists to include the imports of their internal properties.