Drupal 8 version

There is a d8 branch now. I'm attaching some code that I was playing with, might be useful as a starting point for anyone willing to pick up the task.

is there any sandbox or github repo to contribute to?

summary needs update to current state and targets

andypost, looks like there is an 8.x-1.x branch on here that you can submit a patch against.

@nicholas.alipaz the stub code already attached, its just needs to be commited, then it makes sense to fix remains

is there any sandbox or github repo to contribute to?

andypost, I wrote about submitting a patch since you asked the above. You should be able to submit at patch against the 8.x-1.x branch I would assume.

How is the porting going?

Just a friendly reminder, How is the porting going?

I might be interesting in helping with some efforts to port this. Can anyone involved with the initial effort provide a summary of this issue?

btw Here's related d8 module https://www.drupal.org/project/field_states_ui

Oh interesting, thanks for the link.

Hi all!
Gregorio, I represent Adyax company. We started porting the module and finished some base work. We used ideas of conditional_fields and field_states_ui modules. And we would like to share our work. A DEV version could be provided by us in a week.
I would be very pleased if You contacted me as soon as possible.
Also I would like to update this issue https://www.drupal.org/node/2609628 and Kanban board

Olga, it's not clear why and How you gonna port the module instead of collaborate on existing and working field_states_ui?

I see no reason to have 2 modules for the same task, so better to improve existing (field_states_ui) and write upgrade path from conditional_fields and field_conditional_state.

Andrey, we started porting before we have found field_states_ui and unfortunatly it is not finished jet and doesn't work. But the module really helped us! We also decided to save data in display configuration, but we used the logic of conditional_fields module for applying.
So I can't say what project should be chosen. Both of them were created for one task.

Hi, all!
Here is a link to repository with the work we have done. In the master branch You can find working code, that uses conditional fields module's logic. And the field_states_ui branch contains an attempt to use plugin logic from field_states_ui module.
I was inspired to try field_states_ui instead of conditional_fields after your comments. But I faced a problem. The name of default content fields DOM is different from field name, so attached states don't work.
Hope You'll find this code useful!

https://github.com/OlgaRabodzei/conditional_fields

Hi all,

I'm evaluating @OlgaRabodzei 's conditional_fields version and it seems promising.

But looking further, I'd like to avoid picking modules which won't be supported or widely adopted, and the current situation makes it hard to decide...

Is there a consensus among the maintainers ( @peterpoe for conditional_fields and @NickWilde for field_states_ui) on the interest of having a single module for this usage, and if so, on which solution (PHP/display) should be adopted? If not, is anybody committed to release a full version soon and to maintain it in the future?

Anyways, thanks to every dev/maintainer for pushing this feature forward and sharing your work!

Subscribing to follow outcome of discussion. I am working on a site now in which we would like to use this functionality, hopefully in a stable module ecosystem.

Hello everyone,

Yes, Adyax company is willing to maintain this module. Now we are actively working on it and we would be glad to get any help (as developing, testing, reviewing).

Also would you like to create an online conference for discussing the future of all three modules? (Probably using Hangouts.) Could it be on Friday next week?

Sure!
Let it be at 15:00(CET) on Friday 21/10/2016.
So I kindly ask all not indifferent to join the discussion on Friday!
You could ping me on email (orabodzei@adyax.com) for sending an invitation.
Also I'll provide here a link an hour before we'll start.

Hello!
Everyone who wants to take part in the discussion please join us by this link. We are starting at 15:00 (CET)
https://hangouts.google.com/hangouts/_/adyax.com/orabodzei

Hi OlgaRabodzei,

Thank you guys for the great works on Drupal 8 version for this module.

I am a full-time PHP and Drupal developer who can give you a hand on developing on weekend.

I just check the github page https://github.com/OlgaRabodzei/conditional_fields.

The top priority task on the Todo list is 'Use services instead of global functions'. I am happy to undertake this task if you guys need.

Or if there is other developing task I can help, just let me know.

Cheers,

Dear Mingsong,
Sure, we would be glad if You joined to the project! Sorry for the late
answer. You can fork the project on github and after create a merge request.
If You'll have any questions, contact me, I promise answer as soon as
possible next time.
Best regards, Olga.

Hello!
As we didn't get any response from maintainers, I ventured to create the task https://www.drupal.org/node/2827031
Also I decided to assign to me tasks related to Drupal 8 version of this module.

It seems to me that peterpoe hasn't been active in about 8+ months. At this juncture, if he hasn't responded and you have made all the necessary attempts to get in contact with him you can file an issue with the Drupal.org maintainer's issue queue to obtain project access.

OlgaRabodzei, see https://www.drupal.org/node/251466 if you haven't already.

Marking as fixed now that there is a 8.x-1.x-dev release.
Will create a new meta issue for a stable release.