feat(players): add CSV and JSON import templates #82
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
umpire274/bs_scoring!82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/download-import-template"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:
123431b554ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
@ -1152,3 +1164,51 @@ fn display_player_list(players: &[(Player, String)]) {);Selecting the new CSV template option writes a file whose sample data has 10 columns (
team_name,team_code,league_name,...), butimport_csvonly accepts 5, 7, or 8 fields in the orderteam,number,away_number,first_name,last_name,position,pitch,bat. A user who downloads this template and immediately imports it will getInvalid format (expected 5, 7, or 8 fields, got 10)for every data row, so the feature is unusable as a player import template.Useful? React with 👍 / 👎.
The JSON template starts with
team_name, butimport_jsonrequires ateamstring field and rejects records before it can import them. The same template also usesrole/bats/throwswhile the importer expectsposition/bat/pitch, so downloaded JSON templates cannot be imported without manual rewrites.Useful? React with 👍 / 👎.