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

does linking improve performance and what affects does a change have on the component #6695

Closed
PawelSpoon opened this issue Oct 19, 2021 · 4 comments
Labels
question This is more a question for the support than an issue.

Comments

@PawelSpoon
Copy link

Describe the issue

syncing with remote repo seems slow.
i have a project with 70 components, all those components / files are actually in the same folder, belong logically together.
during setup i did not use the link feature but defined all the components separately.

i had to solve a merge issue a way back and there i saw that due to that separate definition i end up with lot of copies of this one folder. so my question: if i define only one component and link all the others to that, will that speed up ?

secondly if i do that, will that break the history, comments etc of the existing components, their translations etc. ?

thanks a lot

I already tried

i did read the docu about linking

To Reproduce the issue
n.a.

@PawelSpoon PawelSpoon added the question This is more a question for the support than an issue. label Oct 19, 2021
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

@nijel
Copy link
Member

nijel commented Oct 19, 2021

It will speed up some operations - the repository does not have to be fetched and updated several times. The parsing of the files will stay the same.

Changing the URL from actual remote to weblate:// one will not break anything. Just make sure that everything is on the same revision before doing that to avoid parsing older files.

@PawelSpoon
Copy link
Author

thank you

@github-actions
Copy link

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue.
Projects
None yet
Development

No branches or pull requests

2 participants