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

Empty XML file generation #555

Closed
HIrena opened this issue Nov 7, 2019 · 3 comments
Closed

Empty XML file generation #555

HIrena opened this issue Nov 7, 2019 · 3 comments

Comments

@HIrena
Copy link

HIrena commented Nov 7, 2019

Hello,

Not really an issue, but is it possible to generate an xml from an existing from-select structure? Creating manually xmls to use paired with a <if-missing> feature could be troublesome.

Thank you!

@Seddryck Seddryck added this to the v1.22 milestone Nov 7, 2019
@Seddryck
Copy link
Owner

Seddryck commented Nov 7, 2019

Fair feedback, creating empty files is boring and not so straightforward.

I propose to add a if-unavailable element in a result-set to specify another result-set if the first one is failing. At the moment, I'll just activate this feature in case an xml-source is failing but feel free to give me some feedback and check if we cannot generalize.

In addition, I'll create a new child element of result-set named empty and accepting an attribute column-count or a list of column-names.

Combining these two new features, it should be easier to create an empty result-set when something is going wrong into your xml-source.

@Seddryck
Copy link
Owner

Seddryck commented Nov 9, 2019

  • new element empty for a result-set
  • new element if-unavailable for a result-set

@Seddryck
Copy link
Owner

Seddryck commented Nov 9, 2019

Beta available at https://ci.appveyor.com/project/Seddryck/nbi/builds/28736908/artifacts or 1.22.0-beta0025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants