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

Need to be smarter about identifying SchemaDef-d types #80

Closed
ghost opened this issue Feb 5, 2020 · 0 comments
Closed

Need to be smarter about identifying SchemaDef-d types #80

ghost opened this issue Feb 5, 2020 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@ghost
Copy link

ghost commented Feb 5, 2020

Right now, if we have

  - class: SchemaDefRequirement
    types:
      - $import: ./BUSCO-assessment_modes.yaml

we don't recognize the definition

    type: BUSCO-assessment_modes.yaml#assessment_modes

because we are doing simple string matching rather than extracting the base name properly.

@ghost ghost self-assigned this Feb 5, 2020
@ghost ghost added the bug Something isn't working label Feb 5, 2020
@ghost ghost added this to the 2020.02.29 milestone Feb 5, 2020
@ghost ghost closed this as completed in a8ee30a Feb 6, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

0 participants