how to help getting this library to work?

[kaystrobach]

• testcases
• .ddev environment for local dev with example project?
• ...

please give a hint, maybe we can figure something out.

[ivarconr]

I think the most critical point is to handle the state caching and updating of that cache. I think that has to be an API provided by the user of this library. State can be stored in database, redis, on disk etc.

[kaystrobach]

So it would be fine having an psr example?

So that you know how to handle that caching stuff?

Do you need a commandController to check for new data as example implementation?

[ivarconr]

Yes I think this would be a good idea.

On Thu, 4 Jul 2019 at 16:37, Kay Strobach notifications@github.com wrote:

So it would be fine having an psr example?

So that you know how to handle that caching stuff?

Do you need a commandController to check for new data as example implementation?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Unleash/unleash-client-php/issues/12?email_source=notifications&email_token=AABGZZE4ZP4KFCOOMMOZQITP5YDKLA5CNFSM4H5RXG6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZHSTZI#issuecomment-508504549, or mute the thread https://github.com/notifications/unsubscribe-auth/AABGZZG3XJVBDOSFFZG4K2TP5YDKLANCNFSM4H5RXG6A .

[kaystrobach]

will try to provide a solution in the next weeks. should not be that hard.

[ivarconr]

Cool, and much appreciated!

I start my summer vacation today, so I've added you as collaborator with write access to allow you to have progress!

[kaystrobach]

thank you, i started on the fork i made and created an easy pr. it should show how easy it is to add caching.

[kaystrobach]

each using framework should add a psr16 cache into the client on creation (construct) and then it should not be to hard to addopt this lib to symfony, flow, zend, etc, als they all have an psr16 compatible cache

[iGitScor]

Hi, do you need any help ?

[kaystrobach]

the question is if we should make a call or something similar to organize the work to be done.

IMHO we should do the following things:

• define goal (should be already done in this ticket)
• define architecture
• define dependencies (PSRs)
• define dev env for dev and test
• build interfaces (i think there are already some well known from unleash and we should stick to them as far as possible)
• add functionallity
• add tests etc.

[ivarconr]

Could we try to coordinate it on slack? Let me know how I can support you.

[kaystrobach]

sure

[frazjp65]

@kaystrobach, @ivarconr, what still needs to be done to get this into a usable state?

[kaystrobach]

There is a rather large PR you may hop on and help testing. I mainly restructure the code and make it psr compliant

[kaystrobach]

And you can sponsor that - make it easier to concentrate on he project