- 25 Apr, 2022 1 commit
-
-
jeremytchang authored
fix: Refactored Go SDK to use Go oauth2 client, added `x-looker-appid` header to Go requests (#1069) Fixes #1027 - Refactored to use Go's standard oauth2 client to handle our client credentials flow. The client will automatically fetch and refresh the token when it is expired. Removed all the manual authorization implementation. - Also updated the the AuthSession to maintain only one client instead of creating a new one per request. As recommended by Go docs. `Clients and Transports are safe for concurrent use by multiple goroutines and for efficiency should only be created once and re-used.` - Added x-looker-appid header with standard go http middleware, the RoundTripper interface. - Removed auth implementation specific tests. Added couple auth sanity tests even though the go client itself is well tested. Updated tests to properly call NewAuthSession to properly create the client.
-
- 22 Apr, 2022 1 commit
-
-
Bryn Ryans authored
-
- 21 Apr, 2022 2 commits
-
-
Bryn Ryans authored
A simplified extension provider does not require a type or generic to identify the sdk required, basically it just gives access to Looker SDK 4.0. Also updates the playground package to demonstrate its use: 1. packages updated. 2. added call to me to demonstrate SDK 4.0 usage. 3. now runs dev server on https. 5. removed unnecessary hot HOC.
-
jeremytchang authored
The RegisterFuzzyDecoders method can lead to a concurrent map write error on concurrent calls to Do(). Also RegisterFuzzyDecoders does not need to be called every time JSON needs to be decoded. It only needs to be called once on package init.
-
- 19 Apr, 2022 2 commits
-
-
Dr. Strangelove authored
* chore: changed hardcoded references to looker version for CI/CD * changed hardcode references to use reuasable actions so that versions only need to be changed in one place * factored out the special handling that is no longer needed for credentials versions. Simpliofied credentials secrets to LOOKERSDK_CLIENT_ID from LOOKERSDK_CLIENT_ID__21_18 and likewise for LOOKERSDK_CLIENT_SECRET. * revert: revert mistaken update * chore: fix call to primary-version
-
nsepetys authored
-
- 18 Apr, 2022 1 commit
-
-
John Kaster authored
This is to clarify the values that are used for tests without having to look at the testUtils file to see what the values mean Tagging this a chore because it's internal and shouldn't cause a version bump
-
- 13 Apr, 2022 4 commits
-
-
John Kaster authored
* fix: update permalinks for exampleMiner.ts Browser permalinks should not end with `.git` in the repository name * update hash for examplesIndex.json
-
dependabot[bot] authored
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846"><code>7efb22a</code></a> 1.2.6</li> <li><a href="https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2"><code>ef88b93</code></a> security notice for additional prototype pollution issue</li> <li><a href="https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d"><code>c2b9819</code></a> isConstructorOrProto adapted from PR</li> <li><a href="https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb"><code>bc8ecee</code></a> test from prototype pollution PR</li> <li>See full diff in <a href="https://github.com/substack/minimist/compare/1.2.5...1.2.6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/looker-open-source/sdk-codegen/network/alerts ). </details> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
dependabot[bot] authored
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846"><code>7efb22a</code></a> 1.2.6</li> <li><a href="https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2"><code>ef88b93</code></a> security notice for additional prototype pollution issue</li> <li><a href="https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d"><code>c2b9819</code></a> isConstructorOrProto adapted from PR</li> <li><a href="https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb"><code>bc8ecee</code></a> test from prototype pollution PR</li> <li>See full diff in <a href="https://github.com/substack/minimist/compare/1.2.5...1.2.6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/looker-open-source/sdk-codegen/network/alerts ). </details> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by:
John Kaster <kaster@google.com>
-
fabio-looker authored
-
- 12 Apr, 2022 3 commits
-
-
Bryn Ryans authored
-
Bryn Ryans authored
-
Bryn Ryans authored
1. pinned to version 1.7.14 as 1.7.15 requires unsupported package. 2. overrode header rule to use a pattern for date. 3. fixed one lodash issue that aroise. 4. ignored nested ternary issues. should be fixed but outside the scope of what I want to do with this change. The next published version of @looker/eslint-config-oss will include the overridden header rule so the overridden header rule can be removed then. Will investigate the unsupported package then.
-
- 08 Apr, 2022 1 commit
-
-
John Kaster authored
-
- 07 Apr, 2022 6 commits
-
-
looker-open-source-automation-bot authored
-
Joel Dodge authored
-
John Kaster authored
Release-please versioning was incorrect so the most critical package to get published didn't get published. Updating the source comment header which should meet the criteria for republishing
-
looker-open-source-automation-bot authored
I have created a release \*beep\* \*boop\* --- <details><summary>sdk-codegen-all: 2.3.1</summary> ### Bug Fixes * encodeParam returned [object Object] for object types ([#1047](https://www.github.com/looker-open-source/sdk-codegen/issues/1047)) ([eccc1dbb](https://www.github.com/looker-open-source/sdk-codegen/commit/eccc1dbb3d64f36e6a06d71a1c3da37d972abd3a)) </details> <details><summary>@looker/sdk-rtl: 21.3.2</summary> ### Bug Fixes * encodeParam returned [object Object] for object types ([#1047](https://www.github.com/looker-open-source/sdk-codegen/issues/1047)) ([eccc1dbb](https://www.github.com/looker-open-source/sdk-codegen/commit/eccc1dbb3d64f36e6a06d71a1c3da37d972abd3a)) </details> <details><summary>@looker/sdk: 22.4.1</summary></details> <details><summary>@looker/sdk-codegen: 21.5.1</summary></details> <details><summary>@looker/extension-sdk: 22.4.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/sdk bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/sdk-node: 22.4.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/sdk bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/code-editor: 0.1.20</summary> ### Dependencies * The following workspace dependencies were updated * devDependencies * @looker/sdk-codegen bumped from ^21.5.0 to ^21.5.1 </details> <details><summary>@looker/extension-sdk-react: 22.4.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/extension-sdk bumped from ^22.4.0 to ^22.4.1 * @looker/sdk bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/sdk-codegen-scripts: 21.3.2</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * @looker/sdk-codegen bumped from ^21.5.0 to ^21.5.1 * @looker/sdk-node bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/wholly-sheet: 0.5.27</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * devDependencies * @looker/sdk-node bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/extension-utils: 0.1.8</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/extension-sdk bumped from ^22.4.0 to ^22.4.1 * @looker/extension-sdk-react bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/hackathon: 22.4.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/code-editor bumped from ^0.1.19 to ^0.1.20 * @looker/extension-sdk bumped from ^22.4.0 to ^22.4.1 * @looker/extension-sdk-react bumped from ^22.4.0 to ^22.4.1 * @looker/extension-utils bumped from ^0.1.7 to ^0.1.8 * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * @looker/wholly-sheet bumped from ^0.5.26 to ^0.5.27 </details> <details><summary>@looker/run-it: 0.9.31</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/code-editor bumped from ^0.1.19 to ^0.1.20 * @looker/extension-utils bumped from ^0.1.7 to ^0.1.8 * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * @looker/sdk-codegen bumped from ^21.5.0 to ^21.5.1 </details> <details><summary>@looker/api-explorer: 0.9.31</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/extension-utils bumped from ^0.1.7 to ^0.1.8 * @looker/code-editor bumped from ^0.1.19 to ^0.1.20 * @looker/run-it bumped from ^0.9.30 to ^0.9.31 * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * @looker/sdk-codegen bumped from ^21.5.0 to ^21.5.1 * devDependencies * @looker/sdk-codegen-scripts bumped from ^21.3.1 to ^21.3.2 * @looker/sdk-node bumped from ^22.4.0 to ^22.4.1 </details> <details><summary>@looker/extension-api-explorer: 22.4.1</summary> ### Dependencies * The following workspace dependencies were updated * dependencies * @looker/api-explorer bumped from ^0.9.30 to ^0.9.31 * @looker/extension-sdk-react bumped from ^22.4.0 to ^22.4.1 * @looker/extension-utils bumped from ^0.1.7 to ^0.1.8 * @looker/run-it bumped from ^0.9.30 to ^0.9.31 * @looker/sdk bumped from ^22.4.0 to ^22.4.1 * @looker/sdk-codegen bumped from ^21.5.0 to ^21.5.1 </details> This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). -
Joel Dodge authored
for https://github.com/looker-open-source/sdk-codegen/pull/1047 when it lands Co-authored-by:
John Kaster <kaster@google.com>
-
John Kaster authored
`@looker/sdk-rtl` was encoding object values like ```ts { created_date: 'this year to second' } ``` as ```ts [object Object] ``` and now the value is JSON stringified instead
-
- 25 Mar, 2022 1 commit
-
-
John Kaster authored
Updated the runtime information on Look#, Looker's C# SDK for .NET
-
- 24 Mar, 2022 2 commits
-
-
looker-open-source-automation-bot authored
-
jeremytchang authored
feat: Revert "Update release-please version, add r-p config for Go, add Go publish CI (#1030)" (#1035) Issue tracking the reason we can't update from v2 to v3 release-please. googleapis/release-please#1348 This reverts commit e597978f.
-
- 23 Mar, 2022 5 commits
-
-
jeremytchang authored
-
jeremytchang authored
-
jeremytchang authored
- Updated release-please to latest v3 from v2 that contains the needed functionality for releasing Go SDK. The breaking changes should not affect us: https://github.com/google-github-actions/release-please-action/releases/tag/v3.0.0 - Setup release-please config to release Go SDK at v0 only.-- To release Go SDK at v1 and above requires automated editing of the module name in go.mod during SDK generation or when release-please creates a release PR. Release-please gi thub issue: https://github.com/googleapis/release-please/issues/1344 -- The repo tag must be in the exact format of "go/vX.X.X". So package-name and tag-separator in release-please-config.json are set accordingly - Setup release-please-manifest to point go sdk to 0.0.1. 0.0.0 is automatically bumped to 1.0.0 ignoring the "pre-major" release-please configs. - Setup a go publish github action that publishes go module to go proxy based off the new tag - Updated go.mod and go.sum with go mod tidy which cleans up dependencies
-
jeremytchang authored
* fix: Go SDK parses response by result type Currently go sdk model generation doesn't support union type for responses like RunQuery. So we cannot parse according to Content Type Header. For now, parse based off model type. We need to update sdk model generation to use interface{} for union types, and then use Content Type Header to parse response accordingly. This will break downstream dependencies. - Added additional integration tests around queries looks and dashboards. - Parse response based of type defined in go sdk models, the result type - Added unit tests - Return error body in addition to error status code. * Added git issue in comment * Added png/svg integration tests and updated integration tests to passing with new 22.4
-
John Kaster authored
Changes: - An id type was being used in a test for int64. All ids are now strings so a different Int64 spec property is used now - Refreshed the spec shadow copy in APIX. Perhaps we can remove this now? - Changed looker doc redirect link pattern to reflect the removal of redirects from `looker.com/docs/r` to the new `docs.looker.com/r`pattern
-
- 22 Mar, 2022 1 commit
-
-
Dr. Strangelove authored
* fix: 22_4 API * fix: Additional fixes in unit tests for Hackathon * fix: python integration tests for string id types * fix: attempt to fix integration test for typescript * fix TS SDK tests for new string IDs * update python config notes, reformat python SDK files * format python/looker_sdk/sdk/api{31,40}/methods.py Co-authored-by:
John Kaster <kaster@google.com> Co-authored-by:
Joel Dodge <joeldodge@google.com>
-
- 17 Mar, 2022 2 commits
-
-
John Kaster authored
Turns out bazel build files have weird `stat`s that break node fs interrogation and hence break declaration miner. This ignores errors reported on directory checking for those offending paths so indexing completes successfully Hope to find a cleaner solution in the future but because this is an internal tool rarely used I don't want to spend more time on it right now
-
jeremytchang authored
-
- 15 Mar, 2022 1 commit
-
-
John Kaster authored
Unit test tweak to support Looker 22.4 API type changes
-
- 14 Mar, 2022 1 commit
-
-
Dr. Strangelove authored
* ci: change workflows to use reusable action for looker versions * fix: change supported-versions@v0.0.1 to @main Using a particular version here is a mistake since this would need to change for every new looker release. Instead use @main so that the supported-versions action will always use the latest version.
-
- 07 Mar, 2022 2 commits
-
-
Joel Dodge authored
Co-authored-by:
Dr. Strangelove <drstrangelove@google.com>
-
Joel Dodge authored
-
- 04 Mar, 2022 4 commits
-
-
looker-open-source-automation-bot authored
Co-authored-by:
Joel Dodge <joeldodge@google.com>
-
Dr. Strangelove authored
* build: reset version action * add filtering on sdk-codegen-all tag Co-authored-by:
Joel Dodge <joeldodge@google.com>
-
Joel Dodge authored
fixes #944 the main fix here is switching from `cattr.register_structure_hook` to `cattr.register_structure_hook_func`. I re-organized some of the code in an effort to reproduce the issue in the test_serialize.py suite but I could not reproduce there, only in integration tests. Now that it's a function, we don't need a generated hook per type. I further isolated the converter usage switching the serializing to use each 31/40 dedicated converter. I also switched to the newer GenConverter. setup testing against python 3.10
-
Dr. Strangelove authored
* chore: set version number * move release-as to top-level for multiple packages now Co-authored-by:
Joel Dodge <joeldodge@google.com>
-