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

A rebel can be added to working groups when imported #84

Open
mhulet opened this issue Oct 16, 2019 · 6 comments
Open

A rebel can be added to working groups when imported #84

mhulet opened this issue Oct 16, 2019 · 6 comments
Assignees

Comments

@mhulet
Copy link
Member

mhulet commented Oct 16, 2019

Our current import (/rebels/imports/new) doesn't allow adding to working groups. We want to have a CSV column for working groups IDs.

@mhulet mhulet added this to the Oct 12-Nov 23 (6 weeks) milestone Oct 16, 2019
@begault
Copy link
Collaborator

begault commented Oct 20, 2019

Hey @mhulet
To begin working on imports, I'd like to take this issue as well.
Do you think it's ok ?

@begault
Copy link
Collaborator

begault commented Oct 20, 2019

Is the following format ok ?
1/2/78/4
Do you have a better proposition for separator ? (depending on your use)

@begault
Copy link
Collaborator

begault commented Oct 20, 2019

Some questions about implementation:

@begault
Copy link
Collaborator

begault commented Nov 1, 2019

@mhulet still interested by taking this issue ;)

@mhulet
Copy link
Member Author

mhulet commented Nov 2, 2019

Damn, I completely missed your previous comments @begault. I will come back to it once I have some time to review your suggestions.

@mhulet mhulet assigned mhulet and begault and unassigned mhulet Nov 2, 2019
@mhulet
Copy link
Member Author

mhulet commented Nov 3, 2019

Thanks a lot @begault.

  • About the format, why not using columns? On the user side, it will be easier to write (and read) than slashes. But maybe you suggested slashes for a good reason.
  • About moving csv_import into a library or a model imports folders: yes, that probably makes sense. I let you decide what's best (my only concern is to keep code readable and easy to maintain).
  • About representers, I have never used them personally but I have been interested in the past in Trailblazer (roar-rails suggests to switch to Trailblazer). My understanding is that architecture would make the code more complex to understand for new contributors, but I may be wrong. Maybe we should start with something small (only one representer) and I'll have a better understanding of representers themselves.

@mhulet mhulet removed this from the Oct 12-Nov 23 (6 weeks) milestone Nov 21, 2019
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

No branches or pull requests

2 participants