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

missing keys for required, multivalued, annotations during linkml-map transformation for in slots #2411

Open
Duanoc opened this issue Nov 11, 2024 · 0 comments
Labels
bug Something that should work but isn't, with an example and a test case. community-generated developer-days smallish tickets that can be considered "maintenance" and fixed within a single session

Comments

@Duanoc
Copy link

Duanoc commented Nov 11, 2024

Describe the bug
I tried to convert a schema like below into a new schema using linkml-map basically renaming the attributes.
In the resulting yaml file the tags required, multivalued and annotations are incomplete. Multivalued and required are copied for the tree_root/Class1 class but not for the Class2. Where as annotations are copied for the classes but not for the slots. It this the correct behavior or a bug?

Version of LinkML you are using
linkml_map-0.3.8

Please provide a schema (and if applicable, a data file) that replicates the issue

classes:
  Class1:
    tree_root: true
    annotations:
      key: value
    attributes:
      att1:
        required: true
        multivalued: true
        annotations:
          key: value
      att2:
        range: Class2
        required: true

  Class2:
    attributes:
      att3:
        required: true
        multivalued: true
        annotations:
          key: value
      att4:
        range: Class2
        required: true
@Duanoc Duanoc added the bug Something that should work but isn't, with an example and a test case. label Nov 11, 2024
@sierra-moxon sierra-moxon added the developer-days smallish tickets that can be considered "maintenance" and fixed within a single session label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that should work but isn't, with an example and a test case. community-generated developer-days smallish tickets that can be considered "maintenance" and fixed within a single session
Projects
Status: No status
Development

No branches or pull requests

3 participants