Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge changes from fork into development branch for review #9

Merged
merged 25 commits into from
Nov 16, 2022

Conversation

elipousson
Copy link
Collaborator

There is a lot in this request so I thought it would be better to merge into a development branch to keep working on it in the main repository and either merge piecemeal or just when it is ready. Here is a quick run-down:

Once this PR is merged, I think we can rename the master branch to main and then start pulling these changes into main.

- refactor: add utility functions for checking gpkg files, connecting to gpkg files, updating tables, and checking for the existence of rows after a query
- refactor: add check_timestamp + fmt_timestamp helper functions
- style: convert to markdown style roxygen
- refactor: switch to use utility functions (e.g. update_gpkg_table)
- docs: add Imports + add contributor
- docs: update function documentation
- feat(read_gpkg): add quiet parameter
- fix(read_gpkg): replace reference to DBI w/ RSQLite
- refactor(amend_timestamp): deprecate verbose arg + rename has_query_rows utility function to  has_query_min_rows
- feat: make data available onLoad
- refactor: move check_table_exists + update_gpkg_table
- refactor(read_gpkg_extension): incorporate reference data for extensions as a lookup table for table_name values
- feat(read_gpkg_extension): add read_gpkg_related_tables variant
- feat: add draft use_gpkg_extension
- refactor: add helper extension_tables and extension_table_names functions
- refactor: update NAMESPACE + DESCRIPTION
- test: add test for read_gpkg_contents + sample empty.gpkg file
@florisvdh
Copy link
Member

Hi Eli, I'll merge right away since indeed your aim is to continue your work in a dev branch here.

BTW an alternative to this PR is defining r-spatial/rgeopackage as an extra remote in your local git repo, and push your branch directly here, but of course that's not needed anymore. You now also have the option to clone the r-spatial repo as new.

@florisvdh florisvdh merged commit 9f23f02 into r-spatial:2022-11-15_development-branch Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants