Re: Lazy fetching role for API clients' objects

G'day nataraj,

I'm guessing this is related to your earlier "Framework for making Moose-compatible object from json" post; providing a link to that would've been appropriate.

Take a look at "Moose: has $name|@$names => %options". The "lazy" and "builder" options would seem to be the most appropriate.

— Ken

Comment on Re: Lazy fetching role for API clients' objects

Replies are listed 'Best First'.
Re^2: Lazy fetching role for API clients' objects by nataraj (Sexton) on Sep 10, 2022 at 08:10 UTC
I'm guessing this is related to your earlier "Framework for making Moose-compatible object from json" post; providing a link to that would've been appropriate. Yes this question came from the same project, but I considered it a completely different question Take a look at "Moose: has $name\|@$names => %options". The "lazy" and "builder" options would seem to be the most appropriate. I know how to implement it on bare Moose. At least have an idea. But I want to make sure there is no ready to use tool for it. This is what this post about	[reply]

Replies are listed 'Best First'.

Re^2: Lazy fetching role for API clients' objects
by nataraj (Sexton) on Sep 10, 2022 at 08:10 UTC

I'm guessing this is related to your earlier "Framework for making Moose-compatible object from json" post; providing a link to that would've been appropriate.

Yes this question came from the same project, but I considered it a completely different question

Take a look at "Moose: has $name|@$names => %options". The "lazy" and "builder" options would seem to be the most appropriate.

I know how to implement it on bare Moose. At least have an idea. But I want to make sure there is no ready to use tool for it. This is what this post about

[reply]