{"action":"opened","issue":{"url":"https://api.github.com/repos/katemalone/mod_0_skills/issues/1","repository_url":"https://api.github.com/repos/katemalone/mod_0_skills","labels_url":"https://api.github.com/repos/katemalone/mod_0_skills/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/katemalone/mod_0_skills/issues/1/comments","events_url":"https://api.github.com/repos/katemalone/mod_0_skills/issues/1/events","html_url":"https://github.com/katemalone/mod_0_skills/issues/1","id":453076853,"node_id":"MDU6SXNzdWU0NTMwNzY4NTM=","number":1,"title":"Assessment Results","user":{"login":"rwarbelow","id":3311609,"node_id":"MDQ6VXNlcjMzMTE2MDk=","avatar_url":"https://avatars3.githubusercontent.com/u/3311609?v=4","gravatar_id":"","url":"https://api.github.com/users/rwarbelow","html_url":"https://github.com/rwarbelow","followers_url":"https://api.github.com/users/rwarbelow/followers","following_url":"https://api.github.com/users/rwarbelow/following{/other_user}","gists_url":"https://api.github.com/users/rwarbelow/gists{/gist_id}","starred_url":"https://api.github.com/users/rwarbelow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rwarbelow/subscriptions","organizations_url":"https://api.github.com/users/rwarbelow/orgs","repos_url":"https://api.github.com/users/rwarbelow/repos","events_url":"https://api.github.com/users/rwarbelow/events{/privacy}","received_events_url":"https://api.github.com/users/rwarbelow/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-06-06T14:53:11Z","updated_at":"2019-06-06T14:53:11Z","closed_at":null,"author_association":"NONE","body":"# Checklist/Rubric\r\n\r\n### Part I: Creating Directories and Files; Initializing Git and Pushing to GitHub\r\n\r\n- [x] I named my directories correctly. \r\n- [x] I named my files correctly.\r\n- [x] I structured my files and directories correctly. \r\n- [x] I made one initial commit.\r\n- [x] I pushed my initial commit to GitHub.\r\n\r\n### Part II: Top Down Design\r\n\r\n- [x] I broke down larger processes into smaller layers.\r\n- [x] I added and committed my changes with a properly formatted commit message starting with a present-tense verb and a capital letter.\r\n- [x] I pushed my changes to Github. \r\n\r\n### Part III: Classes, Objects, Attributes, and Methods\r\n\r\nClass #1 Checklist\r\n- [x] I structured and named my directories and files correctly.\r\n- [x] The four attributes I chose for **Class #1** represent properties or characteristics.\r\n- [x] I identified the data type (string, integer, boolean, array, hash/object, datetime) for attributes in **Class 1**.\r\n- [ ] The four methods I chose for **Class #1** represent behaviors or actions.\r\n> It looks like your method names are nouns. In the case of reader/writer methods, this is fine. However, we want to see behaviors and actions for the methods. An example for Desk would be something like `store_item (adds an item to the storage array)`, etc. \r\n- [x] I described what the methods do in **Class 1**, including which attributes they use or modify.\r\n- [x] I added and committed the `class_1.txt` file **separately** with a properly formatted commit message. \r\n\r\nClass #1 Example Object Checklist\r\n- [x] The object I chose for **Class 1** is an instance of this class. \r\n- [x] I listed the values for each attribute of this object. \r\n- [x] I listed the results of each method for this object. \r\n- [x] I added and committed the `class_1_example_object.txt` file **separately** with a properly formatted commit message. \r\n\r\nClass #2 Checklist\r\n- [x] The four attributes I chose for **Class #2** represent states or characteristics.\r\n- [x] I identified the data type (string, integer, boolean, array, hash/object, datetime) for attributes in **Class 2**.\r\n- [ ] The four methods I chose for **Class #2** represent behaviors or actions.\r\n> (Same note as above)\r\n- [x] I described what the methods do in **Class 2**, including which attributes they use or modify.\r\n- [x] I added and committed the `class_2.txt` file **separately** with a properly formatted commit message. \r\n\r\nClass #2 Example Object Checklist\r\n- [x] The object I chose for **Class 2** is an instance of this class. \r\n- [x] I listed the values for each attribute of this object. \r\n- [x] I listed the results of each method for this object. \r\n- [x] I added and committed the `class_2_example_object.txt` file **separately** with a properly formatted commit message. \r\n\r\n### Assessment Results\r\n- [ ] Technical Ready\r\n- [x] Pending\r\n> You're on the right track. Update your methods for the two classes (and corresponding objects) to reflect actions/behaviors. \r\n- [ ] Not Technical Ready\r\n"}}
{"actor":{"display_login":"rwarbelow"}}