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

Allow updating signals #147

Merged
merged 2 commits into from
Sep 30, 2020
Merged

Allow updating signals #147

merged 2 commits into from
Sep 30, 2020

Conversation

AlbertoSadoc
Copy link

When importing signals if a signal with the same id is found it will update the values instead of inserting a new one.

Related to #145

@nblumhardt
Copy link
Member

Thanks for the PR! This would be a great addition.

Since signal import effectively ignores the Ids of source signals, this could cause some surprising changes in behavior for existing users of the command. Perhaps the new behavior could be enabled through a new flag, such as --merge?

@AlbertoSadoc
Copy link
Author

Yes, that is a great point. I will amend that

@AlbertoSadoc
Copy link
Author

@nblumhardt --merge option added suggested.

@nblumhardt
Copy link
Member

Thank you; looks good, I'll need a few spare minutes to review, but think this is the way to go 👍

@nblumhardt nblumhardt merged commit 782dd12 into datalust:dev Sep 30, 2020
@nblumhardt
Copy link
Member

Thanks again! Sorry about the delay; this will make it into the 2020.3 release.

This was referenced Sep 30, 2020
@danielloczi
Copy link

Hi. I'm facing an issue, which relates to this ticket. The id defined in the imported signal is ignored, and the new signal is getting a different id. Please check this ticket: datalust/seq-tickets#1718

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