dnrops
/
GeoIP2-swift
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
GeoIP2-swift/Sources/Api
History
Adam Rocska 7b487ccc60 In its current state this hackery fits our needs. 
Signed-off-by: Adam Rocska <adam.rocska@adams.solutions>
 		2020-06-11 10:22:15 +02:00
..
Model In its current state this hackery fits our needs. 2020-06-11 10:22:15 +02:00
Record In its current state this hackery fits our needs. 2020-06-11 10:22:15 +02:00
ApiForwarding.swift Intentionally committing crap code. 2020-05-30 22:08:07 +02:00
DatabaseType.swift Work in progress. A pretty neat pattern is emerging. 2020-06-04 13:47:18 +02:00
DictionaryInitialisable.swift Library starts to come into its place. I gotta go through the models & records once again, because de-phpification is pretty hard. Besides that it's all cool and usable so far. 2020-06-10 12:37:38 +02:00
README.md In its current state this hackery fits our needs. 2020-06-11 10:22:15 +02:00
Reader.swift Library starts to come into its place. I gotta go through the models & records once again, because de-phpification is pretty hard. Besides that it's all cool and usable so far. 2020-06-10 12:37:38 +02:00
ReaderFactory.swift System tests ready for execution. Before coverage I'll take another round in the php rat hole to make sure all models are ok. 2020-06-05 16:09:44 +02:00

README.md

Good to know about the API module

It was intentionally designed to reproduce the php scripter fantasies, and awful modeling to reduce risks of having a broken library behavior, and data provision.

Depending on how widespread the library may become, the new fancy API of which I could be proud of will be delivered either :

  • as a backwards incompatible way, by simply throwing it all out in the garbage, and providing a proper professional api
  • as a backwards compatible way, by doing a minor release, marking this pile of shit I wrote as deprecated, providing a neat API module, and throwing this trash in the garbage in the future.