You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is some information about tasks and tests that does not get imported/exported to and from proforma.
This includes for example:
the tasks license
the tasks labels
the testing framework for tests
the private/public setting for tasks
To pick up a draggable item, press the space bar.
While dragging, use the arrow keys to move the item.
Press space again to drop the item in its new position, or press escape to cancel.
What would be the advantage of adding that information to an export?
Since that data is not part of the official ProFormA specification, no tool would use it except CodeHarbor itself. If we reimport the exported data, I'd expect the data in CodeHarbor to be at least up-to-date or even more recent than the exported data. It might make sense if you want to import the task as "new Task", but in that case you could just use the duplicate feature.
Activity
kkoehn commentedon Jun 24, 2024
What would be the advantage of adding that information to an export?
Since that data is not part of the official ProFormA specification, no tool would use it except CodeHarbor itself. If we reimport the exported data, I'd expect the data in CodeHarbor to be at least up-to-date or even more recent than the exported data. It might make sense if you want to import the task as "new Task", but in that case you could just use the duplicate feature.
I don't think this is needed.
MrSerth commentedon Jul 5, 2024
You're right about missing support in the ProFormA standard for everything except the testing framework.
If I see this right, the
unittest
subtype supports specifying a framework and version. This would be something we could add.