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

Xliff-Sync Ignore Workspace Folders without *g.xlf File #111

Open
pri-kise opened this issue Nov 17, 2022 · 2 comments
Open

Xliff-Sync Ignore Workspace Folders without *g.xlf File #111

pri-kise opened this issue Nov 17, 2022 · 2 comments
Labels
effort: medium Initial effort estimate: Medium enhancement New feature or request priority: low Priority estimate: Low

Comments

@pri-kise
Copy link

Right now we are having some workspaces for our apps, that include the MainApp, the TestApp and our .azuredevops (for pipelines only) folder.

Xliff-Sync tries to sync for the .azuredevops folder, too but since it doesn't contain any xlf file, there is always an error shown.
It's not that bad, since the error as catched and only reported in the UI, but this can be misleading for some junior developers.
Maybe the sync process can be improved to ignore such folders...?

@rvanbekkum
Copy link
Owner

Hi @pri-kise,

Thank you for your message.

Just to get a better understanding: why would you want to have the .azuredevops folder as a separate project folder in your .code-workspace file?
I think it might be good that XLIFF Sync maybe skips folders without .xlf files, but still I was curious about that.

@rvanbekkum rvanbekkum added enhancement New feature or request effort: medium Initial effort estimate: Medium priority: low Priority estimate: Low labels Nov 17, 2022
@pri-kise
Copy link
Author

Hi @rvanbekkum
I often have to update the pipelines together with the app.json after some major updates of BC and it is easier to update the required version on every place, if i have the the yaml files are in the same workspace.

I know i could open the yaml files separatly, but I had the experience, that the global search does not always find every result when the files aren't included in my .code-workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: medium Initial effort estimate: Medium enhancement New feature or request priority: low Priority estimate: Low
Projects
None yet
Development

No branches or pull requests

2 participants