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

[Bug] Web encountered an error when method short name is empty #97

Open
reynoldtan opened this issue Jul 24, 2024 · 0 comments
Open

[Bug] Web encountered an error when method short name is empty #97

reynoldtan opened this issue Jul 24, 2024 · 0 comments
Labels
bug - potential For issues describing a potential bug that has not yet been shown repeatable by a core developer.

Comments

@reynoldtan
Copy link
Contributor

Drupal Version

9.4

Tripal Version

4.0.0-alpha1

Module Version

4.x dev (most recent commit)

Site Operating System

Debian Linux

Installation Method

TripalDocker docker

Browsers

Firefox

Observations

In #88.

When uploading traits where the method short name is left out, the validator will not catch the error for the validation summary report in the frontend. Instead, It will throw an exception detailed below:

image

However, when setting the same column header to a blank space, the plugin will catch and report the issue in the frontend.

image

Expected Behaviour

n/a

Steps to Reproduce

With a genus already configured,

  1. in the importer page my site/admin/tripal/loaders/trpcultivate-phenotypes-traits-importer
  2. Click Download a template file link and delete the in file comment.
  3. To reproduce:

A. exception error: In line no. 2, enter value for every column header except Method Short Name. Press tab key at the end of each value entered. When in Method Short Name, press tab key to skip to the next header.

B. To reproduce the passing test: Similar to step no 3-A, but when in Method Short Name, press the space bar once then tab key.

  1. Upload file
  2. Import

Relevant log output

n/a
@reynoldtan reynoldtan added the bug - potential For issues describing a potential bug that has not yet been shown repeatable by a core developer. label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug - potential For issues describing a potential bug that has not yet been shown repeatable by a core developer.
Projects
None yet
Development

No branches or pull requests

1 participant