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

feat(reports): add file type detection #4143

Merged

Conversation

jniles
Copy link
Contributor

@jniles jniles commented Jan 28, 2020

Adds file type detection to the reports archive page so that we are not
proposing to the user to print reports that are not printable (xlsx for
example). It also adds features to provide the correct font awesome
icon depending on the extension to help a user determine which kind of
file they will be downloading.

Example
RZoqUH5TAk

@jniles
Copy link
Contributor Author

jniles commented Jan 28, 2020

This will need to be merged after #4142 to keep things clean.

Adds file type detection to the reports archive page so that we are not
proposing to the user to print reports that are not printable (xlsx for
example).  It also adds features to provide the correct font awesome
icon depending on the extension to help a user determine which kind of
file they will be downloading.
Adds unit tests to the parser functions in the BaseReports file.
@jniles jniles force-pushed the chore-add-file-type-to-report-archives branch from e87c62e to 7a99978 Compare February 3, 2020 15:42
@jniles
Copy link
Contributor Author

jniles commented Feb 3, 2020

bors r+

bors bot added a commit that referenced this pull request Feb 3, 2020
4143: feat(reports): add file type detection r=jniles a=jniles

Adds file type detection to the reports archive page so that we are not
proposing to the user to print reports that are not printable (xlsx for
example).  It also adds features to provide the correct font awesome
icon depending on the extension to help a user determine which kind of
file they will be downloading.

**Example**
![RZoqUH5TAk](https://user-images.githubusercontent.com/896472/73257918-e899a400-41c4-11ea-9898-76bb6bd0a333.gif)


4149: fix(inventory): allow deletion from inventory r=jniles a=jniles

This commit removes the foreign key constraints from the inventory_log
to allow deletion from the inventory.  It also fixes the http headers
sent twice error in the error handler.

Closes #4147.

Co-authored-by: Jonathan Niles <jonathanwniles@gmail.com>
@bors
Copy link
Contributor

bors bot commented Feb 3, 2020

This PR was included in a batch that was canceled, it will be automatically retried

@jniles
Copy link
Contributor Author

jniles commented Feb 3, 2020

bors r-

@bors
Copy link
Contributor

bors bot commented Feb 3, 2020

Canceled

@jniles
Copy link
Contributor Author

jniles commented Feb 3, 2020

bors r+

bors bot added a commit that referenced this pull request Feb 3, 2020
4143: feat(reports): add file type detection r=jniles a=jniles

Adds file type detection to the reports archive page so that we are not
proposing to the user to print reports that are not printable (xlsx for
example).  It also adds features to provide the correct font awesome
icon depending on the extension to help a user determine which kind of
file they will be downloading.

**Example**
![RZoqUH5TAk](https://user-images.githubusercontent.com/896472/73257918-e899a400-41c4-11ea-9898-76bb6bd0a333.gif)


4149: fix(inventory): allow deletion from inventory r=jniles a=jniles

This commit removes the foreign key constraints from the inventory_log
to allow deletion from the inventory.  It also fixes the http headers
sent twice error in the error handler.

Closes #4147.

Co-authored-by: Jonathan Niles <jonathanwniles@gmail.com>
@bors
Copy link
Contributor

bors bot commented Feb 3, 2020

@bors bors bot merged commit 7a99978 into IMA-WorldHealth:master Feb 3, 2020
@jniles jniles deleted the chore-add-file-type-to-report-archives branch February 4, 2020 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants