search

Accenture / sfmc-devtools-copado

SFMC DevTools made easy using Copado Multi-Cloud's webinterface
MIT License
8 stars 2 forks source link

[BUG] retrieve in retrieveTable should return folders #211

Closed JoernBerkefeld closed 2 years ago

JoernBerkefeld commented 2 years ago

as of now we skip folders because that would mean we need to cache folders and process the metadata at least for that - which takes time. however, knowing the folder something is in provides valuable context and hence we should add that. also, the standard "User Story Metadata" entry offers the field Directory to store that - we would need to know what the field name needs to be for that though.

image

maybe we can limit it to something during the commit step, in which we get the full metadata anyways? depends on how these records are created. any thoughts @nrabe-copado ?

nrabe-copado commented 2 years ago

The Directory field is to store the relative directory name of the element .

so, if you have a commit with two changes:

README.md src/main/index.js

... then for the first item the Directory would be empty "", because it is in the root of the git repository. and for the index.js file, Directory="src/main"

JoernBerkefeld commented 2 years ago

Understood - only that it is not auto filing that. My guess is that it is based on the response that our retrieveTable is sending to the commit overlay when we confirm the cimmit message- we send the list of files but without ab attribute for the directory

JoernBerkefeld commented 2 years ago

turns out it's the "m" field. found it here https://docs.copado.com/articles/#!copado-ci-cd-publication/executing-a-copado-action

image