Re: Documenting best practices

On Tue, Mar 13, 2018 at 3:18 PM, drmikecrowe wrote: > So, having 2 objections to clones, let me give my thoughts: > ​I regretted disparaging clones as I did. They may be just what you want. There is a lot of tricky code behind clones, but from the user (api) perspective

Re: Documenting best practices

So, having 2 objections to clones, let me give my thoughts: - What I'm working on is a microservices design spec that has multiple API's with apps that interact with those API's - Let's say the API has a function 'PUT /updatePosition' that takes these arguments - ID -

Re: Documenting best practices

On Tue, Mar 13, 2018 at 8:41 AM, drmikecrowe wrote: I have a lot of configuration that must be defined as a Javascript object > (or JSON). I'm trying to decide on the best way to enter it into Leo. > ​For such questions I think first of creating a Leo script.​ ​Whether

Re: Documenting best practices

To enter this kind of data manually I'd look at YAML, which can be converted to JSON as needed. I'd be cautious using clones to sync. data / resources across a project. Edward uses clones for the specific case of managing views of code within Leo, which they do well, although there are