API Discussion

[mozharovsky]

What does this thread stand for?

This issue has been created to discuss things you don't like in the current API or ideas on API improvement. If you haven't read our News and/or Changes issues, we strongly recommend you to do it now, so you can understand how things are likely to work in version 2.0.0.

Structure

We'd like to keep a general form of your feedback, thus we ask you to use the following structure:

1. General description of a change/suggestion (please give us links if you've borrowed ideas)
   1. Why you think it's necessary to rework;
   2. How it makes experience/performance/feel&look better
2. Code sample showing state before and after
3. Your personal recommendations

We highly appreciate your support!

[sprint84]

I appreciate your communication and dedication.
If you are looking for contributors, I'm willing to dedicate some of my spare time to the project.

[cyrilzakka]

I'd love to dedicate some of my spare time for this as well

[mozharovsky]

@sprint84, @Archivus: Guys, thank you for being interested in this project, we'd be glad to see you on board. :]

We use Slack for communication. Please give me your actual email addresses so I can send you invitations.

[sprint84]

guime.sprint@gmail.com

[cyrilzakka]

cyril.zakka@gmail.com

[mozharovsky]

@sprint84, @Archivus: Done! Please check out your inbox.

[mozharovsky]

@Archivus: Are you with us? :]

[pavelhiq]

@mozharovsky Have you come to any conclusion and when do you expect the 2.0 release to become available? :)

[elsesiy]

@pavelhiq Unfortunately we can't name you a date or even a time span since there'll be a major refactoring and feature improvements. We're working hard on it :)

[dbmrq]

#264 might be better left for version 2.
While we're at it, I think it would be better if all CVCalendar classes and typealiases had the CV prefix, otherwise it would prevent users that add the code directly to their project to define many classes they could want to.