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

Add Link rules to metadata.json in export archive #3360

Closed
CasperWA opened this issue Sep 27, 2019 · 1 comment · Fixed by #3386
Closed

Add Link rules to metadata.json in export archive #3360

CasperWA opened this issue Sep 27, 2019 · 1 comment · Fixed by #3386

Comments

@CasperWA
Copy link
Contributor

In order to:

  • better help debugging export/import issues and
  • keep information concerning how the archive was created,

I suggest we add a small dictionary to the archive's metadata.json file that simply states the rules used to generate the particular archive.
This may look something like:

{
  "link_rules": {
    "input_calc_forward": false,
    "input_calc_backward": true,
    "create_forward": true,
    "create_backward": true,
    "return_forward": true,
    "return_backward": false,
    "input_work_forward": false,
    "input_work_backward": true,
    "call_calc_forward": true,
    "call_calc_backward": false,
    "call_work_forward": true,
    "call_work_backward": false
  },
  // ...
}
@CasperWA CasperWA self-assigned this Sep 27, 2019
@CasperWA CasperWA added this to To do in Import/export via automation Sep 27, 2019
@CasperWA CasperWA added this to To do in Release 1.0.0 via automation Sep 27, 2019
@CasperWA
Copy link
Contributor Author

CasperWA commented Oct 2, 2019

Idea by @sphuber: If the goal is to have the best point from which to do debugging, one may consider to add the entities that are originally specified to be exported as well.

I agree, since the rules are somewhat meaningless without them. Indeed, one may consider to add all relevant user-changeable parameters.

@CasperWA CasperWA moved this from To do to In progress in Release 1.0.0 Oct 4, 2019
Import/export automation moved this from To do to Done Oct 11, 2019
Release 1.0.0 automation moved this from In progress to Done Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Import/export
  
Done
Release 1.0.0
  
Done
Development

Successfully merging a pull request may close this issue.

1 participant