Skip to content

Conversation

@jensstalder
Copy link
Contributor

Semantic versioning

This PR is a Minor (non-breaking change, adds functionality or feature)

Generall things to consider

  • I have read the CONTRIBUTING.md document.
  • If my change requires documentation, I added it already.
  • I have added tests to cover all my changes.
  • All new and existing tests pass.

List of issues related to this PR

Added

  • priceRange feature back
  • xyz

@markus-codechefs
Copy link

@jensstalder I'm assuming from your commit messages that the proposed change will not work and the PR can be closed?

@jensstalder
Copy link
Contributor Author

No, just an additional validation test for min and max which is only possible with xml 1.1. The PR still implements the new fields, it's just not as thoroughly validated.

@jensstalder jensstalder linked an issue Oct 16, 2020 that may be closed by this pull request
@jensstalder jensstalder self-assigned this Oct 26, 2020
@jensstalder jensstalder added the Feature Request Missing functionality and changes label Oct 26, 2020
@jensstalder jensstalder added the Business need unclear Business cases are being discussed but not decided yet. label Dec 7, 2020
@jensstalder
Copy link
Contributor Author

<price> is required this makes this a bit weird.
We need to discuss why and how this will be implemented

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

Labels

Business need unclear Business cases are being discussed but not decided yet. Feature Request Missing functionality and changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Price range was in CasaXML but seams to be missing now.

2 participants