The goal should be to only have one package for each top-level module and
that that package should implement a complete API that correctly models
whatever the thing is.

It seems clear how to do that for things like `Color`, `Html`, `Array`,
`Date`, etc.  I think in the examples Peter gave, `Style` is not a clear
concept and shouldn't be a top-level module.  What is a "Style"?  To know
what a style means, you need to know what is being styled.  From a brief
look at the package docs, it seems like the modules should be named
something like `Html.Animation` and `Html.Composable.Style` instead of
`Style`.

On Fri, Jun 10, 2016 at 8:36 PM, Ian Mackenzie <[email protected]>
wrote:

> I think some sort of guideline for module names would be good, similar to
> what exists in the Java or .NET worlds - I've been using an
> 'Organization.Package.Module' scheme for my (yet to be published) code.
> Easy enough to use 'import as' to shorten things up.
>
>
> On Saturday, 11 June 2016 06:52:10 UTC+10, Yosuke Torii wrote:
>>
>> I'm curious about it too.
>>
>> For library authors, there seems no way to check duplication
>> automatically.
>> Is this a new issue, or is there a guideline about module names?
>>
>>
>> 2016年6月10日金曜日 21時55分35秒 UTC+9 Peter Damoc:
>>>
>>> I want to use
>>>
>>> mdgriffith / elm-style-animation / Style
>>> and
>>> seanhess / elm-style / Style
>>>
>>> How does one handles such situations?
>>>
>>> The modules do something completely different and are complementary
>>> somehow.
>>>
>>>
>>>
>>> --
>>> There is NO FATE, we are the creators.
>>> blog: http://damoc.ro/
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Elm Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to