Skip to content

chore: replace var with const/let in repo#119

Merged
aeschright merged 1 commit intonpm:release-nextfrom
watilde:feature/let-const
Jan 9, 2019
Merged

chore: replace var with const/let in repo#119
aeschright merged 1 commit intonpm:release-nextfrom
watilde:feature/let-const

Conversation

@watilde
Copy link
Copy Markdown
Contributor

@watilde watilde commented Dec 14, 2018

@watilde watilde requested a review from a team as a code owner December 14, 2018 20:39
@watilde watilde changed the title chore: replace var with const/let chore: replace var with const/let in repo Dec 14, 2018
@zkat
Copy link
Copy Markdown
Contributor

zkat commented Dec 14, 2018

Please split this up into two PRs. I can take the docs PRs more easily than code ones, too.

@watilde
Copy link
Copy Markdown
Contributor Author

watilde commented Dec 15, 2018

I just splitted into the two here and #120.

Copy link
Copy Markdown
Contributor

@aeschright aeschright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⭐️

@aeschright aeschright changed the base branch from latest to release-next January 9, 2019 22:06
@aeschright aeschright merged commit 73a3edf into npm:release-next Jan 9, 2019
aeschright pushed a commit that referenced this pull request Jan 10, 2019
aeschright added a commit that referenced this pull request Jan 10, 2019
aeschright pushed a commit that referenced this pull request Jan 18, 2019
@watilde watilde deleted the feature/let-const branch December 2, 2019 17:06
Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
…pm#134)

Previously used dirs::config_dir() which resolves to different paths per
OS (~/Library/Application Support/gws on macOS, %APPDATA%\gws on Windows),
contradicting the documented ~/.config/gws/ path and causing users to place
config files in the wrong location (ref npm#119).

Now uses ~/.config/gws/ everywhere with a fallback to the legacy OS-specific
path for existing installs. Also consolidates duplicated dirs::config_dir()
calls in auth.rs and discovery.rs to use the central config_dir() helper.
Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
…#119) (npm#127)

Admin-only scopes (apps.*, cloud-identity.*, ediscovery, directory.readonly,
groups) require Workspace domain-admin access and cannot be granted to personal
@gmail.com accounts — Google returns 400 invalid_scope when they're included.

Changes:
- Add is_workspace_admin_scope() helper (mirrors is_app_only_scope())
  to identify scopes that fail for personal Google accounts
- Exclude these scopes from the template_selects of the 'Recommended' preset
  in run_discovery_scope_picker()
- Exclude them from the resolved scope list when the Recommended template
  is confirmed
- Add 8 unit tests covering the new helper

Workspace admins can still access these scopes via 'Full Access' template
or by selecting them individually in the picker.

Note: this is complementary to PR npm#108 which filters alertcenter scopes
at the API-discovery level. This PR handles the broader set at the
recommendation layer.

Addresses npm#119 (Bug 1: admin scopes in Recommended preset)

Co-authored-by: Claude <noreply@anthropic.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.

3 participants