Use interface name as component namespace #12

tengstrand · 2018-10-27T11:10:37Z

This is a breaking change for workspaces that have multiple component implementations for an interface.
Fixes:
#6
#10

not both interface name and component name as before.

* Handle system and "Polylith exceptions" in a cleaner way. * Updated the help for 'sync'. * Updated CircleCI config. (#8) * Accept non vector import statements (#11) * Use interface name as component namespace (#12) * Updated version to 0.2.0.

Always use only the interface namespace name as component namespace,

17cd9f4

not both interface name and component name as before.

tengstrand added the enhancement label Oct 27, 2018

tengstrand self-assigned this Oct 27, 2018

tengstrand requested a review from furkan3ayraktar October 27, 2018 11:10

tengstrand added this to In progress in Polylith via automation Oct 27, 2018

Merge branch 'develop' into feature/use_interface_name_as_package_name

32991ec

furkan3ayraktar approved these changes Oct 27, 2018

View reviewed changes

Polylith automation moved this from In progress to Reviewer approved Oct 27, 2018

tengstrand merged commit 785c2ab into develop Oct 27, 2018

Polylith automation moved this from Reviewer approved to Done Oct 27, 2018

tengstrand deleted the feature/use_interface_name_as_package_name branch October 27, 2018 16:13

tengstrand mentioned this pull request Oct 27, 2018

Release/v0.2.0 #13

Merged

furkan3ayraktar mentioned this pull request Nov 20, 2018

Sync fails when using a different implementation of the same interface in a system #27

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use interface name as component namespace #12

Use interface name as component namespace #12

tengstrand commented Oct 27, 2018 •

edited

Use interface name as component namespace #12

Use interface name as component namespace #12

Conversation

tengstrand commented Oct 27, 2018 • edited

tengstrand commented Oct 27, 2018 •

edited