COMPASS-3851: ability to add fields when exporting collection

[lrlna]

Description

Current work going into being able to Select Fields when exporting.

So far this PR:

• separates the three stages of exporting: select query vs. full collection, selecting fields, selecting output
• keeps error message throughout all stages and will render above the Back, Close, {PROCEED} buttons
• fields selected are kept in props, so when a user goes back to selecting fields, their previously selected/disselected fields are still there
• if a user goes back to SELECT FIELDS modal state after having exported, they can edit fields, and export again (dunno if anyone will actually do this, but just in case)

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added

Open Questions

Currently I am finding one document and grabbing the initial fields to render from that document. Should I instead do a collection sample and run schema-parser over that to get a more accurate selection of fields. I can't determine if that's an overkill, or, in fact, a more detailed solution.

Help! I can't figure out why my export-select-fields component is not rerendering. At this point I am being very impolite towards React, but I am sure there is a simple thing I am not seeing.

I am thinking I will do + ADD FIELD button in another PR, so people can play around with this for now and tell me if everything works ok.

Types of changes

• Minor (non-breaking change which adds functionality)

[lrlna]

@imlucas this is the PR that has the three step flow for export!

[imlucas]

@imlucas this is the PR that has the three step flow for export!
@lrlna awesome thanks!

[imlucas]

Currently I am finding one document and grabbing the initial fields to render from that document. Should I instead do a collection sample and run schema-parser over that to get a more accurate selection of fields. I can't determine if that's an overkill, or, in fact, a more detailed solution.

I've been thinking the same for import

Help! I can't figure out why my export-select-fields component is not rerendering. At this point I am being very impolite towards React, but I am sure there is a simple thing I am not seeing.

Let's pair up. Nothing sticking out cause.

I am thinking I will do + ADD FIELD button in another PR, so people can play around with this for now and tell me if everything works ok.

Sounds good

[lrlna]

Currently I am finding one document and grabbing the initial fields to render from that document. Should I instead do a collection sample and run schema-parser over that to get a more accurate selection of fields. I can't determine if that's an overkill, or, in fact, a more detailed solution.

I've been thinking the same for import

Hang on, so are you sampling or doing a find one?

Thanks for a kick-ass review, btw!

[imlucas]

@lrlna

Hang on, so are you sampling or doing a find one?
Doing equivalent of findOne() today → adding a todo to think about schema/sampling someday if that ends up being too limited

[imlucas]

Oh and I was thinking more about "export-select-fields component is not rerendering" last night. If this is still a problem w/ not rerendering make it an array of includeFields: ['_id', 'foo', etc...] then convert it into an object in your reducer when passing it to data-service.

[lrlna]

@imlucas solved the re-render issue, and oh my god was is it the most nuanced react thing.

so what i had before here was:

const fields = this.props.fields;

which I then modified and updated the redux state with. So this is considered a mutation by redux, so it will just give up and not fire a re-render apparently \o/

using Object.assign() gets rid of the mutation and creates a brand new thing i can rewrite.

[imlucas]

Ah! Sweet! Nice find

[lrlna]

@imlucas i fixed everything we talked about IRL yesterday, let me know if it looks good to merge!