Skip to content

Commit

Permalink
Update NEWS/TODO
Browse files Browse the repository at this point in the history
  • Loading branch information
lsteinmann committed Nov 23, 2023
1 parent c3d7b28 commit 7124746
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 6 deletions.
1 change: 1 addition & 0 deletions .Rbuildignore
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,4 @@
^docs$
^pkgdown$
^profile$
TODO.md
16 changes: 10 additions & 6 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,17 @@
# idaifieldR 0.3.3 _2023_05-25_ (wip)
* fix problem in `reformat_geometry()` (MultiPolygons have to be unnested before processing)
* additionally, imported polygons may be formatted improperly, unnest if necessary (`reformat_geometry()`)
* `remove_config_names()` can issue a message about duplicate fields if it is appropriate - this may prevent accidental creation of multiple columns with the same name, as e.g. 'diameter' and 'projectName:diameter' may both have existed in the data after redefining or updating a field in the project configuration. This may need a check and attempt to merge the data (or not merge it). #TODO this produces absolutely horribly long messages.
* #TODO: better solution for handling geometry overall
# idaifieldR 0.3.3 _wip_
### New features
* Add `idf_last_changed(connection, n = n)`: Returns a vector with the last n changed resources in the database.
* Add `idf_get_changes(connection, ids = c(...))`: Returns a data.frame in which each change to one of the resources listed in ids (can be either their 'identifier' or 'UUID') corresponds to one row separated by creation or modification.
* `remove_config_names()` issues a message about duplicate field or category names if it is appropriate. Functions may override data when multiple columns with the same name would otherwise exist, as e.g. 'diameter' and 'projectName:diameter'. Attaches an attribute that lists the duplicate field/category names.

### Minor changes
* Notify of new / different version on GitHub on attaching the package (`check_idaifieldr_version()`).

# idaifieldR 0.3.2 _2023_04-15_
### Fixes
* Fix problem in `reformat_geometry()` (MultiPolygons have to be unnested before processing). (Imported Polygons may be formatted improperly, unnest if necessary (`reformat_geometry()`). Geometry is still a *work in progress*.)
* Fix a bug in `get_field_index()`, where it would return an empty data.frame if there was no configuration-resource.

# idaifieldR 0.3.2 _2023-04-15_
* add option to use or not use exact dates as min/max values for dating if present
* add `idf_json_query()` which lets users construct their own queries to the CouchDB-API
* improve and export `find_layer()`
Expand Down
19 changes: 19 additions & 0 deletions TODO.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# TODO

## In general
* Better structure of tests with less specialized cases?

## for v0.3.4 ?
* Handling geometry does not work very well and should be reconsidered. Maybe
by importing some package like sf and storing the geometry as sf-objects,
though this seems overkill. Or keep original JSON-string somehow to be useable
GeoJSON...?
* `remove_config_names()` may or may not overwrite data with the information
from unused fields, and I have to check that, though I have not yet noticed
any problem.

## for 1.0.0
* Getting CRAN-ready: Better structured tests that do not depend on DB-connections.
* Reduced messaging behaviour.
* Reduced functions, make it easier to maintain somehow.
* Clean up old code.

0 comments on commit 7124746

Please sign in to comment.