Conversation
|
blocked by #1889 , i guess. |
|
Some jobs of CI on Azure is failing with unknown reason and some are canceled somehow. |
|
force rerun resolved everything. |
|
@weiznich It's ready to review. |
diesel_cli/src/cli.rs
Outdated
| .short("o") | ||
| .long("only-tables") | ||
| .help("Only include tables from table-name") | ||
| .conflicts_with("only-table-regexes") |
There was a problem hiding this comment.
The next release will be 2.0 so we can make a breaking change here. Therefore I would prefer to just introduce this functionality under the old flags.
cc @diesel-rs/core as information.
There was a problem hiding this comment.
What does the old flags mean?
There was a problem hiding this comment.
I'm thinking of just replacing the old flag (only-tables) with the regex filtering.
diesel_cli/src/main.rs
Outdated
| let filter_regex = matches | ||
| .values_of("table-name-regexpes") | ||
| .unwrap_or_default() | ||
| .map(|table_name_regex| Regex::new(table_name_regex).unwrap().into()) |
There was a problem hiding this comment.
Could we print a nicer error message here if the provided string is no valid regex?
(Hint: If that map returns a Result it is possible to collect into a Result<Vec<_>, _>)
|
fixed message. And also, I found the filtering is referencing non-existent argument. Thus fixed to refer |
|
Nightly tests are failing because try_from has been stabilized. It's not relevant to this PR |
|
wait on #2108 |
Maybe travis isn't up-to-date? |
Implement #1911
To hold backward compatibility, added new fields
*_table_regexes.