Skip to content

Issue 716: custom tsconfig.json file name #784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

henkerik
Copy link
Contributor

@henkerik henkerik commented Dec 2, 2024

Changes are visible to end-users: yes

  • Searched for relevant documentation and updated as needed: no
  • Breaking change (forces users to change their own code or config): no
  • Suggested release notes appear below: yes
# gazelle:js_tsconfig_file _tsconfig_json_

Path to the `tsconfig.json` file, in case your TSConfig file has a different file name

Test plan

  • New test cases added: bazel test //gazelle/js:tsconfig_custom_file_name_test

@jbedard
Copy link
Member

jbedard commented Dec 2, 2024

Awesome, thanks for implementing this! 👍

@jbedard jbedard closed this Dec 3, 2024
jbedard added a commit that referenced this pull request Dec 13, 2024
Synced from #784 by
henkerik:

---

### Changes are visible to end-users: yes

- Searched for relevant documentation and updated as needed: no
- Breaking change (forces users to change their own code or config): no
- Suggested release notes appear below: yes

```
# gazelle:js_tsconfig_file _tsconfig_json_

Path to the `tsconfig.json` file, in case your TSConfig file has a different file name
```

### Test plan

- New test cases added: `bazel test
//gazelle/js:tsconfig_custom_file_name_test`

Closes #784

Co-authored-by: Henk Erik van der Hoek <mail@henkerikvanderhoek.nl>
GitOrigin-RevId: b773c2626f32ffa826f85ed52e31472acad93a7c
jbedard added a commit that referenced this pull request Dec 14, 2024
Synced from #784 by
henkerik:

---

### Changes are visible to end-users: yes

- Searched for relevant documentation and updated as needed: no
- Breaking change (forces users to change their own code or config): no
- Suggested release notes appear below: yes

```
# gazelle:js_tsconfig_file _tsconfig_json_

Path to the `tsconfig.json` file, in case your TSConfig file has a different file name
```

### Test plan

- New test cases added: `bazel test
//gazelle/js:tsconfig_custom_file_name_test`

Closes #784

Co-authored-by: Henk Erik van der Hoek <mail@henkerikvanderhoek.nl>
GitOrigin-RevId: b773c2626f32ffa826f85ed52e31472acad93a7c
gregmagolan pushed a commit that referenced this pull request Dec 15, 2024
Synced from #784 by
henkerik:

---

### Changes are visible to end-users: yes

- Searched for relevant documentation and updated as needed: no
- Breaking change (forces users to change their own code or config): no
- Suggested release notes appear below: yes

```
# gazelle:js_tsconfig_file _tsconfig_json_

Path to the `tsconfig.json` file, in case your TSConfig file has a different file name
```

### Test plan

- New test cases added: `bazel test
//gazelle/js:tsconfig_custom_file_name_test`

Closes #784

Co-authored-by: Henk Erik van der Hoek <mail@henkerikvanderhoek.nl>
GitOrigin-RevId: b773c2626f32ffa826f85ed52e31472acad93a7c
gregmagolan pushed a commit that referenced this pull request Dec 15, 2024
Synced from #784 by
henkerik:

---

### Changes are visible to end-users: yes

- Searched for relevant documentation and updated as needed: no
- Breaking change (forces users to change their own code or config): no
- Suggested release notes appear below: yes

```
# gazelle:js_tsconfig_file _tsconfig_json_

Path to the `tsconfig.json` file, in case your TSConfig file has a different file name
```

### Test plan

- New test cases added: `bazel test
//gazelle/js:tsconfig_custom_file_name_test`

Closes #784

Co-authored-by: Henk Erik van der Hoek <mail@henkerikvanderhoek.nl>
GitOrigin-RevId: b773c2626f32ffa826f85ed52e31472acad93a7c
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