Thomas Bell

icon indicating a website link https://thomasbell.io/ icon indicating an email [email protected]

icon location salt lake city, UT icon location A digital systems engineer with nearly 14 years of experience. Interested in the intersection of infrastructure and digital product development.

Results 6 comments of Thomas Bell

Fixed issue with multiple levels of json objects

The reason I didn't store the object on the controller, is because my use case is somewhat more dynamic. We are using fancytree.js which does not support conventional angular bindings....

Fixed issue with multiple levels of json objects

I realized actually that I missed a case; specifically a multi-level json object such as {r1:1, r2:{ rs1:1, rs: 2}}. This will not work and will still have a parse...

Fixed issue with multiple levels of json objects

I have resolved the parsing issue by including jison compile a parser. This way we have a comprehensive way to parse callback args. In the case of json, it treats...

Fixed issue with multiple levels of json objects

I wrote a couple of test cases for the issue that I ran into, they are named as follow; "should parse json arguments as json", "should parse json objects along...

Fixed issue with multiple levels of json objects

@KylePDavis Can you elaborate on point 1? I have a test case that specifically tests for a literal argument: "should parse json objects along with non json objects"

Terraform is not able to find the desired provider for datadog. Could not retrieve the list of available versions for provider hashicorp/datadog: provider registry registry.terraform.io does not have a provider named registry.terraform.io/hashicorp/datadog

I have this same problem with the datadog provider. My provider setup looks like the following: ```sh terraform { required_providers { aws = { source = "hashicorp/aws" version = "~>...