Reactive store and components

When a data is updated on the store by a GET, a PATCH, a PUT or a POST, it should tell the components that are making use of that resource, so that they update their UI accordingly.

This issue is one of the most problematic one regarding the SIB app. It creates a lot of UX problems in the app, and working around them has proven to be nearly impossible.

By Alexandre on 2019-11-18T18:59:26 (imported from GitLab project)

I guess we need to settle down on a store solution first.

I understand. What are the steps to reach a conclusion?

Do we have other options than LDFlex? Why is the current solution not good enough?

By Alexandre on 2019-11-19T17:22:37 (imported from GitLab project)

We're not using LDFlex right now. So the question is the other way around: Should we get back to it?

I need to plan a call with Ruben and probably Inrupt to discuss that.

@sylvain: You meant a phone, no?

By Alexandre on 2019-11-19T17:45:56 (imported from GitLab project)

what?

Which plan do you need?

By Alexandre on 2019-11-19T17:57:26 (imported from GitLab project)

the plan of planning a call...

I see... we can probably help you with that.

By Alexandre on 2019-11-19T18:02:14 (imported from GitLab project)

UP :-)

By Alexandre on 2019-11-21T11:31:21 (imported from GitLab project)

There won't be any progress on this in any near future. I suggest you keep using the workarounds for now.

@sylvain: There are no workaround for the SIB APP from what @matthieu and @jbpasquier told me. It is turning all administration feature unusable.

One thing we can do is trigger an app refresh on edition. That's dirty as fuck but that would work.

By Alexandre on 2019-11-21T12:02:03 (imported from GitLab project)

@matthieu @jbpasquier can you explain to me where there's no workaround for this?

I'm available for a call if it helps.

@alexandre what do you mean by there is no workaround?
I agree that there is no easy fix, but solutions exists. As @jbpasquier did in the sib-app, when a resource is updated:

• on save, do sibForm.component.resource.clearCache() where sibForm is the form you used to edit the resource -> remove the resource from the cache
• sibDisplays.forEach(sibDisplay => sibDisplay.data-src = sibDisplay.data-src) where the sibDisplays are all the component which are related to this resource -> reload all the sibDisplays to fetch the new resource

Is it something you can do on u4e?

@matthieu: We did nothing on the SIB APP. At the moment, edition is unusable. See this discussion here https://git.happy-dev.fr/startinblox/applications/sib-app/issues/269, and with @jbpasquier for more details.

By Alexandre on 2019-11-21T13:22:55 (imported from GitLab project)

I didn't published that, reload the whole app was really slow (Understand in seconds). Should I?

@jbpasquier : It seems we don't have the choice to trigger a app refresh if the framework isn't ready. We can't assume the user will understand that the newly created circle, or the newly added member, or what not, is actually here but not really here until she manually refreshes the app.

By Alexandre on 2019-11-21T13:24:40 (imported from GitLab project)

I'm not sure to understand. What we discussed together has been deleted @jbpasquier? If not, we had a working example right? Or not fully functional maybe?