jaymodi98/Sync-Ends

Issues

• Add tests for main.py

  #58 opened 4 years ago
  1

• Update sync_ends_service test to fix common add and delete message structure

  #54 opened 4 years ago
  1

• Make universal display message structure in `get_newly_added_message` and `get_delete_message`

  #52 opened 4 years ago
  0

• Modify hard coded directory structure using standard library methods

  #46 opened 4 years ago
  2

• Add tests for sync_ends_service.py

  #45 opened 4 years ago
  0

• Add tests for parser.py

  #44 opened 4 years ago
  2

• Add config file parameter in CLI arguments instead of passing a bunch of parameters

  #43 opened 4 years ago
  2

• CLI does not terminate its run

  #39 opened 4 years ago
  3

• Add code coverage checks in travis

  #37 opened 4 years ago
  0

• Add description of pattern used in README

  #35 opened 4 years ago
  1

• Add 'What' documentation in code

  #34 opened 4 years ago
  6

• Git ignore fixes

  #32 opened 4 years ago
  0

• Add tests for EndPoint class

  #28 opened 4 years ago
  0

• Update zenodo badge and readme to remove old project's details

  #27 opened 4 years ago
  2

• Add postman collection files, editor related files and data folder to gitignore

  #26 opened 4 years ago
  1

• Add Slack API token as CLI input argument

  #24 opened 4 years ago
  2

• Create setup.py

  #23 opened 4 years ago
  3

• Clean up etc folder

  #22 opened 4 years ago
  2

• Add Testing for Collection class

  #19 opened 4 years ago
  2

• Create and add promo video to readme

  #17 opened 4 years ago
  0

• Add installation of requirements.txt to setup.py

  #15 opened 4 years ago
  1

• Add API tokens for slackbot and Postman

  #14 opened 4 years ago
  2

• Add steps to setup, install and run deployment environment.

  #12 opened 4 years ago
  2

• Compile code on local machine.

  #11 opened 4 years ago
  0

• Put the code on Travis to automate the testing of the code

  #10 opened 4 years ago
  2

• Use a data storage mechanism (secure database) to store API collection details.

  #9 opened 4 years ago
  6

• Packaging of the code for easy distribution.

  #8 opened 4 years ago
  2

• Implement the script as a CLI which can be easily downloaded from PIP distribution

  #7 opened 4 years ago
  1

• Check if all tools are installed and configure linters, code formatters

  #6 opened 4 years ago
  2

• Implement the logic to find the difference in the old and new schema and post meaningful message on slack channel

  #5 opened 4 years ago
  3

• Add test cases to improve the code coverage and better testing of code

  #4 opened 4 years ago
  4

• Refactor the code to make it neat and clean

  #3 opened 4 years ago
  2