lucasverra / b-b Goto Github PK

https://www.useloom.com/share/2f672f7a9d9b4b6980b5f3a9fba0d66e

view here

also as seen in video

to mee its to big, @tmsmldr what do you say ?

in Firefox and in chrome after darg&dropin the file, if the file has errors, the blue button will not appear but the errors aren't displayed

Please check spec file for ressources and comment here on our improvement for upload page.

Since you didn't start on layouting, we thought of this mod. Is this ~ same level of complexity? @gsanikidze

There is a new column , oos for out of stock

• add check on /upload : every item should be NOT empty on that column
• remove that item from /filter page if oos is yes
  INPUT Template - Test Valide Simple - Avec OSS.xlsx

loader does not finish eve with one line

http://recordit.co/6ge9WtYSOK.gif

some help on CORS => https://livebook.manning.com/#!/book/cors-in-action/chapter-1/1

Couleur, Couleur pied, Catégorie, Tissu

can you make it text or number but NOT scientific notation ?

we do not provide basic error image workflow.
if assets is not found (bad url), excel files is not created.

we should return in the cell :

• error , 404

or

• error, not an image

or

• error timeout (after 90s)

File is here : INPUT template global - CORINNE COBSON + chaises.xlsx
Hey there @gsanikidze , im trying to upload a new file from client and get the "invalid structure" error.

I wish to understand what is failing as a check. How to debug ?

I want to be able to assist final user on the import file mods it has to do

should be wider to reduce impact on image/ cell height

export file should be named “B&B_ficher_offre_BRAND_DDMMYY(date)_XXX”

🙃

use this input file as reference =>
INPUT template global - CORINNE COBSON + chaises - modif Tomas.xlsx

With product in hands of final customer, we got small feedbacks : In spec document we asked you to remove a column (towards the right side) called couleur.

Final client got confusing so here is the proper spec :

• DO export couleur column
• remove from export couleur polish column

http://g.recordit.co/2EwSFT3GLe.gif

should start desabled on new filter box

when click on next button nothing happens

safari 11 OK
chrome OK lastest version
im on firefox lastest version

can you try that please ?

App should be buildable and testable by stakeholder,so netlify.com is our choice. You should be able to commit new changes and let netflify should build automatically

@gsanikidze

As seen in video https://www.loom.com/share/28e9117035994cf1954e4275c4ecb852,

when i click on a button, that specific model box moves automatically to the bottom of the layout . That is not OK

as it stands, the monochrome background color can bring confusion. Please inspire yourself from specification for applying a greyscale as a feature to differentiate models / hierarchy

URL should impact directly without proxy.

colors and first line

=> all textes are centered horizontal & vertical in cell

Today, no check is done regarding this column. Please add same check as other columns

Add Contrôl on column "Couleur pied" > Same check already made for "Couleur", "Type/ Categorie Produit", "Tissu/Materiau"

@gsanikidze
You are showing all uniq values and not the one related to the model specifically

Same is happening in color attribute (ex: Kendal model is showing creme value, but that value is not available in excelfor Kendal model)

video here => https://www.useloom.com/share/527225611f1445c9b227bb1c638bbdc7

in plain words :

there is some form of complementarity between attributes from one box to another box (of the same model). That is not good 🆘

in the video it's clear that attributes selected in 2nd box have an impact on counting in the first box.
I think you'r implementation is treating the model as the lowest level, when you should use the individual box as the lowest level of [counting+selection model item from buttons activity]

Specification
There are 2 differents types of record-counting actions that the app have to perform

Record counting of the selection of an individual box
Record counting of the total records that will be exported.

These actions has to be performed automatically and triggered by any change on the state of the buttons selection.

Each box should have its own count and the total count will be presented at the bottom of the page

Criteria selection and counting logic.

On Individual Boxes

Each box use the same logic to count the number of records that meet the criteria defined by the button selection. The only thing that could change from one box to another is eventually the model that is defined in the section.

The state of the selection buttons will be used to populate a query asking the database for the count of the records that meet the criteria. The conditional criteria used is a simple “OR” and “AND” logic.

Between values of the same attribute there will be an “OR” type of condition
Between Attributes of the individual bor there will an “AND” type of condition

In other words. For each box, the app should ask the data base to count only for the records that correspond to a particular model but only if they have, ANY of the colours selected but only if they have, ANY of the type of furniture selected but only if they have, ANY of the tissues selected, but only if they have, ANY of the pieds selected.

If no value is selected for an attribute then the system should ask for an empty or null value in that attribut.

Ex GET Records or COUNT Records
Box 1 > Model [M1] AND Color [ c1 OR c2 OR, ... ] AND Category [ cat1 OR cat2 OR, ... ] AND Toucher [ t1 OR t2 OR, ... ] AND Pieds [ p1 OR p2 OR, ... ]

Right now the total counter at the bottom of the selection page only counts the selection made on the first selection box for each model an doesn't count the selection made with boxes that are added.

https://www.loom.com/share/cb7550ee6a674b27845a83ba151af891

please check this

they need to be removed