-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Proposal for the introduction of extensions (#537)
* extract all changes from previous * fixup * allow hyphens in extension names * fixup hyphens * only require one toolbox that implements extension * specify how to work with multiple PEtab problems * specify we do not require a quorum number of votes * allow test cases to be provided by the extension library * Apply suggestions from code review Co-authored-by: Daniel Weindl <[email protected]> Co-authored-by: Daniel Weindl <[email protected]>
- Loading branch information
1 parent
992a278
commit 617431c
Showing
7 changed files
with
131 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
|
||
name: PEtab Extension | ||
about: Suggest a new extension for PEtab core | ||
title: '' | ||
labels: file format | ||
assignees: '' | ||
|
||
--- | ||
|
||
**Name of the Extension** | ||
Please make sure that the extension name matches the regular expression `^[a-zA-Z_]\w*$`. | ||
|
||
**Which problem would you like to address?** | ||
A clear and concise description of which use case you want to address and, if applicable, why the current specifications do not fulfill your requirements. | ||
|
||
**Describe the solution you would like** | ||
A clear and concise description of the changes you want to propose. Please describe any additional fields / files you would want to add, including allowed inputs and implications. | ||
|
||
**Describe why this should not be implemented by changes to PEtab core** | ||
A clear and concise description in what way the proposed changes introduce features that are orthogonal to the PEtab core specification. | ||
|
||
**List the extension library that implements validation checks** | ||
A link to the website or github repository that accompanies the proposed extension. | ||
|
||
**List the toolboxes that support the proposed standard** | ||
A link to the website or github repository that contains the software that implements support for the standard. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters