Skip to content
Snippets Groups Projects

simplify record representation, prettier decription in print_info and method to write zenodo json

Merged Vuillaume requested to merge repr into master
1 unresolved thread

Merge request reports

Pipeline #138141 passed

Pipeline passed for ed246455 on repr

Test coverage 76.00% (0.00%) from 1 job
Approved by
Test summary results are being parsed

Merged by Enrique GarciaEnrique Garcia 3 years ago (Oct 6, 2021 7:46am UTC)

Merge details

  • Changes merged into master with 7b43805f (commits were squashed).
  • Deleted the source branch.

Pipeline #139170 failed

Pipeline failed for 7b43805f on master

Test coverage 71.00% (0.00%) from 1 job

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
432 433 return f"Record #{self.id} : {self.title}"
433 434
434 435 def __repr__(self):
435 return json.dumps(self.data, indent=4, sort_keys=True)
436 return f"Record({self.id})"
  • Hhmm, I liked the json reprensentation of a Record. But maybe is just me ^^. Could we maybe keep the write_zenodo and add a print_zenodo method ?

  • It's very long and a bit annoying when doing interactive work, no?

    Printing the metadata is just doing print(record.data) - do we need a function for that?

  • record.data will print all the Record class, not only the metadata. It was just a suggestion.

  • Please register or sign in to reply
  • Enrique Garcia approved this merge request

    approved this merge request

  • Enrique Garcia mentioned in commit 7b43805f

    mentioned in commit 7b43805f

  • Please register or sign in to reply
    Loading