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.

Sign up for GitHub

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

Jump to bottom

[ENHANCEMENT] Add a field rename stragegy in SchemaEntryType #35

Closed
harryle95 opened this issue May 12, 2024 · 1 comment
Closed

[ENHANCEMENT] Add a field rename stragegy in SchemaEntryType #35

harryle95 opened this issue May 12, 2024 · 1 comment
Assignees
@harryle95
Labels
current Issues to be focused on in the current milestone enhancement New feature or request
Milestone
Create a basic wo...

Comments

@harryle95
Copy link
Collaborator

Summary
Describe the new feature you want to be added

At the moment, referencing fields - i.e. investigationId are renamed at the component level. While this is fine for many cases, the current ad-hoc solution is cumbersome for vocabulary references. For generality, it's simpler to have another field in the schema rather than to transform the field in-situ at component creation level.

Example
Provide an example or use-case of the requested feature

TBA
@harryle95 harryle95 added enhancement New feature or request current Issues to be focused on in the current milestone labels May 12, 2024
@harryle95 harryle95 self-assigned this May 12, 2024
@harryle95
Copy link
Collaborator Author

Closed given PR#36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@harryle95 harryle95

Labels
current Issues to be focused on in the current milestone enhancement New feature or request
Projects
None yet
Milestone
Create a basic working version of mia...
Development

No branches or pull requests
1 participant
@harryle95