Skip to content

feat: Always generate path resolver#14

Merged
hermanschaaf merged 1 commit intofeat/cqv2_wipfrom
path-resolver
Aug 25, 2022
Merged

feat: Always generate path resolver#14
hermanschaaf merged 1 commit intofeat/cqv2_wipfrom
path-resolver

Conversation

@hermanschaaf
Copy link
Copy Markdown
Contributor

By always generating a path resolver, we can eliminate uncertainty about what the original field name was.

@hermanschaaf hermanschaaf merged commit 575016d into feat/cqv2_wip Aug 25, 2022
@hermanschaaf hermanschaaf deleted the path-resolver branch August 25, 2022 06:58
yevgenypats added a commit that referenced this pull request Aug 30, 2022
* feat: Remove connection spec

* fix SourceSpec

* working on destination plugin

* added bunch of tests

* remove limit from sdk

* Added more tests

* remove dead code

* fix some linters

* feat: Using json everywhere apart from yaml for the user

We are taking a similar approach to k8s to use json internally
for marshalling/unmarshalling and yaml only for using facing stuff.

yaml parsers are much more complex and also have tons of vulnerabilities
so we want to use json everywhere where there is a machine reading those configurations.

* more work around configuration

* tests working again

* Implement code generation helpers

* improvments to codegen

* fix: dont override nil values

* more fixes to base templates

* more codegen improvments

* feat: Support timestamp columns (#12)

* Always generate path resolver (#14)

* fix: NewTableFromStruct pointer to time.Time (#15)

* feat: Add WithDescriptionEnabled to NewTableFromStruct

I suggest not to use it as it is just duplicated bloat and
it is super slow

* Add table descriptions (#17)

* detect duplicate columns on start

* fixed golang-lint

* run gci

* more linting

Co-authored-by: Herman Schaaf <hermanschaaf@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants