Jalali day is out of valid range about shamsi_date HOT 9 CLOSED

Oh,
I have an idea
:D

Maybe it is a problem of the date picker library you were using !
Since shamsi_date is stateless, but the date picker may be related to the date you are using it ...

from shamsi_date.

So I will close this issue,
Since it is not related to shamsi_date.

I also opened an issue on the calendar ui library which you where using ...

from shamsi_date.

Hi,
I think the reason is when you add 3 months to 1400/05/31 you will get
1400/08/31 and in shamsi calendar only the first 6 months have 31 days
but the next months have less days (either 30 or 29) so this is an invalid date.

for your next statement about changing date,
can you provide complete example ?

from shamsi_date.

Nothing new... Just instead of 1400/05/31 I used 1400/05/20:

Jalali date;
var initDate = '1400/05/20';
var splitDate = initDate.split("/");
var date1 = Jalali(int.parse(splitDate[0]), int.parse(splitDate[1]), int.parse(splitDate[2]));
date = date1.addMonths(3);      -------------> The line that exception happens

from shamsi_date.

import 'package:shamsi_date/shamsi_date.dart';

void main() {
  final d = Jalali(1400, 05, 20);
  print(d);
  print(d.addMonths(3));
}

this results in:

Jalali(1400, 5, 20)
Jalali(1400, 8, 20)

what version of shamsi_date are you using ?

from shamsi_date.

Yes this is working fine today
The exception was only happening on 1400/05/31 as I said:

The point is this is ONLY happening today at 1400/05/31 (8/2/2021) and was working fine the other days

on 1400/05/31, no matter what date I tried addMonths on.... the result was the mentioned exception anyway

Im using shamsi_date: ^0.15.0

from shamsi_date.

please make an issue for that library and add the link here ...

from shamsi_date.

Hmm thanks I will sure do that.

And about this:

I think the reason is when you add 3 months to 1400/05/31 you will get
1400/08/31 and in shamsi calendar only the first 6 months have 31 days
but the next months have less days (either 30 or 29) so this is an invalid date.

is this related to the date picker too?
Or is it a bug at all?! if not how should I handle it

from shamsi_date.

It is not a bug !
it is the correct behavior !

from shamsi_date.