Good morning! I started writing down what I'd like a dependency catalog to make possible. Based on ...

# amper

[louiscad]

Good morning!
I started writing down what I'd like a dependency catalog to make possible.

Based on that, I drafted a short sample.
I'm sharing it to see what folks, and the Amper team think about it.
Feel free to tell your thoughts and ideas!

[amakeev]

Thank for sharing Louis! Could you give some comments ? What would you like to be possible in the dependency catalogs?

[louiscad]

Yep, I will, I have already written down a bunch of things in a Google Doc (where this screenshot is from)

Shall I write the comments here, or share the doc link? @amakeev

[amakeev]

It’s up to you

[louiscad]

Here's a link to my draft:
https://docs.google.com/document/d/1IgTTTl5nDjAXqEUxv6Ug_ZJKZZAPJAo5Phy7EJOkfvg/edit?usp=drivesdk

Feel free to request access to comment on it. Discussing it here is fine too.

I'll probably update it later on to explain the why of every part of the syntax. If you have questions in the meantime, please let me know!

[amakeev]

Thanks for the link, Louis, without additional explanations it’s hard to interpret the code snippet. But the goals sections is a valuable source of use-cases. Would be interesting to learn how you prioritize those.

[louiscad]

I added comments on about all the parts of that snippet in the Google doc. They should give a rationale for all the cases.

[louiscad]

@amakeev I just added some prioritization things at the beginning of the "Goals" section, also.

[amakeev]

Thanks! we are right now looking into the design for the Amper-specific catalog and this list of use-cases/wishes is quite handy

[louiscad]

Hello! Has this been any useful? I have high hopes for dependency catalogs and ease of upgrading, and I wonder what's gonna come out in that area in Amper 🙂

[amakeev]

Louis, we have a fist design draft for Amper catalogs. They will generally resemble Gradle’s catalogs, but the first version will be rather simple:

• Project libraries are declared in the project file libraries section.
• Each library has a name and is declared using the same DSL as the dependencies:
project.yaml file:

libraries:
  # define a "junit" maven library using a short form
  junit: org.junit:junit:4.12
  
    # define an "alamofire" CocoaPod library using its default DSL 
  alamofire:
    pod: 'Alamofire'
    version: '~> 2.0.1'

Later we might expand the functionality.

This design is not yet implemented, I expect it to be available not earlier then after KotlinConf