Skip to content
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

Remove importPaths option #1389

Merged
merged 1 commit into from
Mar 29, 2023

Conversation

FranzBusch
Copy link
Member

Motivation

In #1373 (comment), we added a new option to the SPM plugin config file that allows passing custom import paths (aka search paths) to protoc. Recently, I wanted to try this out but found out that this was not working as expected.

  1. The option is configured "globally" across invocations. That doesn't really compose with the way we have structured the other settings
  2. The option expects absolute paths right now which makes it almost impossible to use.

I propose to remove this option again from the main branch so we are not shipping it with the 2.0 release. In the PR, I asked the adopter if he is actually using that and confirmed that it isn't working like he expected it to work and wasn't using it.

Modification

Remove the importPaths option again.

# Motivation
In apple#1373 (comment), we added a new option to the SPM plugin config file that allows passing custom import paths (aka search paths) to protoc. Recently, I wanted to try this out but found out that this was not working as expected.

1. The option is configured "globally" across invocations. That doesn't really compose with the way we have structured the other settings
2. The option expects absolute paths right now which makes it almost impossible to use.

I propose to remove this option again from the main branch so we are not shipping it with the 2.0 release. In the PR, I asked the adopter if he is actually using that and confirmed that it isn't working like he expected it to work and wasn't using it.

# Modification
Remove the `importPaths` option again.
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