Regression issue with forest-express-sequelize 6.6.1

Help me!
#1

Hi team,

I was testing the latest forest-express-sequelize 6.6.1 release, and I have discovered a regression issue.
=> All of my related hasMany relations do not display any more in parent collections

Here is an example:
I have a native devices collection with has a Many to many relationship with t_users collection.

When displaying the Users related data section of a specific device, no record is displaying.

  • It is working fine in forest-express-sequelize 6.6.1
  • but it does not work with forest-express-sequelize 6.6.0

The returned results from my server are identical in both cases.

Here is the video that illustrates the display change between 6.6.0 and 6.6.1.

Hoping this will help to identify the bug.

Best regards

#2

Hello @Louis-Marie

Thanks a lot for your very detailed feedback, and for having identified the version with the issue.

Can you just confirm that it’s working correctly with version 6.6.0 and not working anymore with version 6.6.1 as you wrote the opposite in your post?

I opened a bug on our side, we will work on it as soon as possible.

#3

Hi @GuillaumeGautreau,

Yes I confirm (sorry for my mistake).

  • It is working fine in forest-express-sequelize 6.6.0
  • but it does not work with forest-express-sequelize 6.6.1

Best

#5

Hello @Louis-Marie,

We have just released the 6.6.2 version of forest-express-sequelize.
It will fix the issue you encountered :tada:

Tell me if everything is ok for you :grinning_face_with_smiling_eyes:

2 Likes
#6

Hello @Guillaume_Cisco,

Thank you for this update.

I have just tested it and it solves that issue, thank you.
However, I have still another new regression issue that I have described in a new ticket here.

This new issue is linked to forest-express-sequelize 6.6.2.
It was not present in 6.6.0.

Best regards

#7

Hello @Louis-Marie :wave:

First of all, thanks a lot for the feedbacks, it really helps out !

Sorry for the inconvenience, I will close this ticket as it is fixed, someone is jumping on the second ticket you linked in your previous message.

Thanks.

Steve.