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

Case sensitive tags/attributes #37

Closed
gersak opened this issue May 6, 2016 · 2 comments
Closed

Case sensitive tags/attributes #37

gersak opened this issue May 6, 2016 · 2 comments

Comments

@gersak
Copy link

gersak commented May 6, 2016

Hi,

I'm working on project where we are using hickory as part of our client interface towards REST backend application. Backend is providing XML that contains case sensitive tags that refer to JAVA classes.

Hickory has hardcoded cast of attribute names and tags to lower-case-keyword. Is it possible to make it more transparent and leave that job to end user. To use zipper/walk to change keys?

Tnx,
Robert

@davidsantiago
Copy link
Collaborator

I'm not sure. Hickory assumes HTML throughout the pipeline, and I really
don't know that much about XML, so I haven't thought about the extent to
which you can send XML through there. Do you have a specific change in
mind, or are you asking if I know how to make it happen? Answer to the
second one is no, I'm afraid.

On Friday, May 6, 2016, Robert Gersak [email protected] wrote:

Hi,

I'm working on project where we are using hickory as part of our client
interface towards REST backend application. Backend is providing XML that
contains case sensitive tags that refer to JAVA classes.

Hickory has hardcoded cast of attribute names and tags to
lower-case-keyword. Is it possible to make it more transparent and leave
that job to end user. To use zipper/walk to change keys?

Tnx,
Robert


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#37

@gersak
Copy link
Author

gersak commented May 6, 2016

Hi,

Tnx for quick feedback. I've found out that similar issue has already been opened.
#22

So I guess that olivergeorge is already working on it. Tnx, as far as I'm concerned issue is closed...

@gersak gersak closed this as completed May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants