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

Default nucleotide and amino acid sequence #454

Closed
Taepper opened this issue May 29, 2024 · 0 comments · Fixed by #510 or #514
Closed

Default nucleotide and amino acid sequence #454

Taepper opened this issue May 29, 2024 · 0 comments · Fixed by #510 or #514
Assignees

Comments

@Taepper
Copy link
Collaborator

Taepper commented May 29, 2024

The default nucleotide and amino acid sequence, that is used when it is omitted in queries, should be better configurable.

  • it is not possible to set a default amino acid sequence. This should be added to the database config.
  • the default nucleotide sequence is main. The default should be unset. A null should be treated as unset.
  • It should be verified that the default sequence exists in the provided dataset.
@fengelniederhammer fengelniederhammer self-assigned this Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
So that we can bring the testdata closer to the test.
Having separate files for every test case seems tedious.

Refs: #454
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 16, 2024
fengelniederhammer added a commit that referenced this issue Jul 17, 2024
So that we can bring the testdata closer to the test.
Having separate files for every test case seems tedious.

Refs: #454
fengelniederhammer added a commit that referenced this issue Jul 17, 2024
fengelniederhammer added a commit that referenced this issue Jul 17, 2024
fengelniederhammer added a commit that referenced this issue Jul 17, 2024
fengelniederhammer added a commit that referenced this issue Jul 17, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
So that we can bring the testdata closer to the test.
Having separate files for every test case seems tedious.

Refs: #454
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
So that we can bring the testdata closer to the test.
Having separate files for every test case seems tedious.

Refs: #454
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
fengelniederhammer added a commit that referenced this issue Jul 18, 2024
This was referenced Jul 18, 2024
davidgicev pushed a commit that referenced this issue Aug 4, 2024
So that we can bring the testdata closer to the test.
Having separate files for every test case seems tedious.

Refs: #454
davidgicev pushed a commit that referenced this issue Aug 4, 2024
davidgicev pushed a commit that referenced this issue Aug 4, 2024
davidgicev pushed a commit that referenced this issue Aug 4, 2024
davidgicev pushed a commit that referenced this issue Aug 4, 2024
@github-actions github-actions bot mentioned this issue Aug 6, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants