Fix export to not rely on datamap col A and master being the same #18

Closed
opened 2019-11-24 16:59:17 +00:00 by yulqen · 1 comment
yulqen commented 2019-11-24 16:59:17 +00:00 (Migrated from github.com)

Oh dear - the current implementation of export relies on col A of the datamap being the same as col A in ther master, which is obviously not fit for purpose at all. Clearly you need to be able to adapt the datamap file to your needs (by hiding/omitting rows, as discussed in the comments above), and rely on the key names matching for a value to be exported.

What's your timescale to get this fixed?? This is obviously crucial and I will prioritise the fix.

Originally posted by @hammerheadlemon in https://github.com/hammerheadlemon/datamaps/issues/4#issuecomment-557907105

Oh dear - the current implementation of `export` relies on col A of the datamap being the same as col A in ther master, which is obviously not fit for purpose at all. Clearly you need to be able to adapt the datamap file to your needs (by hiding/omitting rows, as discussed in the comments above), and rely on the key names matching for a value to be exported. **What's your timescale to get this fixed??** This is obviously crucial and I will prioritise the fix. _Originally posted by @hammerheadlemon in https://github.com/hammerheadlemon/datamaps/issues/4#issuecomment-557907105_
yulqen commented 2019-11-25 16:46:33 +00:00 (Migrated from github.com)
Issue fixed with https://github.com/hammerheadlemon/datamaps/issues/4
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
yulqen/bcompiler-engine#18
No description provided.