raheelahmad / hubba

A Github client as a playground for developing some Core Data + Networking patterns.

Hello 👋

I am an iOS engineer, currently working as a Staff Engineer @calm. Besides iOS, I enjoy working on graphics and backend.

---

My main side project currently is Muziqi, an iOS audio player for those who own their music.

hubba's Issues

UIImage category for asynchronous network fetch

UpdateWithRemoteInfo should update relationship's property

If SLPerson.company --relationship--> SLCompany,

and SLPerson has mapping {.. company.name : company_name ..} (local : remote)

and we update SLPerson with updateWithRemoteInfo:{.. company_name : Fitbit ..},

then person.company should have value Fitbit.

Support endPointForObject (example in SLUser)

This will allow a fetch for each object.

This is quite different: assumes these objects are already present, so have been fetched from a different endpoint.

Update a to-one relationship with a separate endpoint

Example: support SLUser.repository relationship mapped to SLRepository.

Relationship cardinality should be set up by `addRelationship`

UpdateWithRemoteInfo should update relationships (to-many)

If SLCompany.persons --relationship--> SLCompany,

and SLCompany has mapping {.. persons : persons ..} (local : remote)

and we update SLCompany with updateWithRemoteInfo:{.. persons : [ "a list of person dictionaries" ..},

then company.persons should have those objects set up and updated.

A basic key-based, disk & in-memory image store

(When needed) Support multiple mappings for properties (for multiple endpoints)

Basically, will have to iterate over the mappings array in + refresh.

Update a to-many relationship with a separate endpoint

Example, support SLUser.repositories relationship to SLRepository

Fetch repositories via relationships from user

• Limit how wide of a graph we fetch when fetching relationships. Right now:
  • fetch User.followers, get Users; fetches User.followers, and so on... (each fetches User.repositories as well, growing the graph even more.
• Remove setting the propertyMappings for a relation mapping (they are inferred from destination class' remoteMapping)

Fetch issues

• A way to provide transformers (currently need a transformer from string → date for createdAt etc.)

---

Getting a "not found" when accessing issues. Maybe non-default scope may be needed.

Solution: scope did not have to be specified. Real problem was that /repos/:owner/:repo/issues needs the owner and repo names not id's !!!

Fetch private repositories for logged in user