Skip to content

Releases: sekgobela-kevin/mimap

mimap v0.3.1

04 Nov 08:40
Compare
Choose a tag to compare
mimap v0.3.1 Pre-release
Pre-release
  • Bugs fixes,
  • Tests added
  • Pemap version pinned(#3)

mimap v0.3.0

02 Oct 08:23
Compare
Choose a tag to compare
mimap v0.3.0 Pre-release
Pre-release
Added 'pemap' support

Support for pemap library was added even if it may pose problems. Pemap has
releasing breaking changing which mimap is currently using. Code that is available
on pemap was removed from mimap. Remeber that most of pemap code comes from mimap
but some of that code still exists in mimap.

Block could not use pemap due to lot of methods to be implemented. Its not easy as item
since block contain lot of method containing "*priority" while pemap contains "*value".
This release has dependency and wheather it works would depend on its dependency and how
it uses it.

Its bad idea that mimap inherit classes of pimap instead of compositing them. It could cause
issues if private attributes get changed or removed which would break the new classes.

If problems arise, it would be better to revert to version that does not depend on pemap.

mimap v0.2.0

30 Sep 10:43
Compare
Choose a tag to compare
mimap v0.2.0 Pre-release
Pre-release

Refactor & Improvements

Mimap library was planned to be library for associating object with priority.
But now there is a need for mimap like library but not associating objects
with priorities.

Similar classes to existing ones were added to try to make library more general.
The same classes were also used by existing classes which resulted in a lot
of changes without changing high level api.

As time goes on, priority features of mimap will be removed and only generic
classes remain. New library for priorities will be developed based on mimap
and it will also use the new mimap.

mimap v0.1.0

30 Sep 10:31
Compare
Choose a tag to compare
mimap v0.1.0 Pre-release
Pre-release
Update: source files

Priority is now optional but exception ill be raised if priority
is not provided when neccessary. If priority is not provided, it
is retrieved from object if not the exception get raised.

This applies to when creating item or block. This comes with limitation
of that None will be taken as if priority is not provided. That means
None wont be supported as priority as it already has another meaning.

Issues
------
- .get_item*() and find_item*() functions are returning None when item cannot
  be found. This would make it as if None is the item that was found but instead
  it should raise exception.

Progress
--------
- This is the final commit for release even if it contain issues.
- Neccessary features for first release have been added.
- The release is not production ready as there may be bugs.
- Thats because the project has no tests and it was not even tested manually.