[yast-devel] Meeting about XML parser future
Hi, I would like to arrange meeting about future of XML parser as we discuss on review and planning meeting. I propose to have it next Tuesday after daily call if everyone interested has a time. And topics? Two main ones: improvements for SLE15 SP3/Leap 15.3 and roadmap for further future. Result of both topics should be trello cards with clear goals. SP3 topics: - discuss if all quirks mentioned in respective trello card make sense and if not, if we can remove it ( as example skipping content of hash and array if it contain nil, removing non string keys in hash, etc ) - discuss if we can depend on nokogiri - see https://github.com/yast/yast-yast2/pull/1039#issuecomment-614441891 - and related what to do with schema validation in SP3 Roadmap topics: - schema validation in long term - use cases for xml parser - approach for xml parser - serializer versus easy writting of xml for users - error handling Proposed Attends: - whoever is interested in topic - ideally Imo and Schubi as autoyast is big xml parser user - lslezak as he knows a lot about usage in control files - mvidner as he knows a lot about old xml parser Any other ideas and how does time fit for you? Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Thu, Apr 16, 2020 at 10:25:55AM +0200, josef Reidinger wrote:
Hi, I would like to arrange meeting about future of XML parser as we discuss on review and planning meeting. I propose to have it next Tuesday after daily call if everyone interested has a time.
Good! -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner
On 2020-04-17 14:21, Martin Vidner wrote:
On Thu, Apr 16, 2020 at 10:25:55AM +0200, josef Reidinger wrote:
Hi, I would like to arrange meeting about future of XML parser as we discuss on review and planning meeting. I propose to have it next Tuesday after daily call if everyone interested has a time.
Good!
+1 -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Thu, 16 Apr 2020 10:25:55 +0200
josef Reidinger
Hi, I would like to arrange meeting about future of XML parser as we discuss on review and planning meeting. I propose to have it next Tuesday after daily call if everyone interested has a time.
And topics? Two main ones: improvements for SLE15 SP3/Leap 15.3 and roadmap for further future. Result of both topics should be trello cards with clear goals.
SP3 topics:
- discuss if all quirks mentioned in respective trello card make sense and if not, if we can remove it ( as example skipping content of hash and array if it contain nil, removing non string keys in hash, etc ) - discuss if we can depend on nokogiri - see https://github.com/yast/yast-yast2/pull/1039#issuecomment-614441891 - and related what to do with schema validation in SP3
Roadmap topics:
- schema validation in long term - use cases for xml parser - approach for xml parser - serializer versus easy writting of xml for users - error handling
Proposed Attends:
- whoever is interested in topic - ideally Imo and Schubi as autoyast is big xml parser user - lslezak as he knows a lot about usage in control files - mvidner as he knows a lot about old xml parser
Any other ideas and how does time fit for you?
Josef
Here are meeting minutes what we decided: First is proposal and after dash is conclusion. Proposal for SP3 ---------------- - use nokogiri for now and have simple schema validation - OK - always export type - OK - add nil type - no, raise exception when nil is passed - hash key type? - no, exception when non-string is used as hash key - empty value with specified type is not nil, but empty value ( either "" or {} ) - OK for list, hash and string, but raise exception for symbol, integer and boolean and also if type is missing - invalid values for types - raise exception - have namespaces only optional, but export it. Links are not valid, is it problem? - OK, invalid links is not problem. Future ------- Decided to postpone after more clear future of autoyast as its main user and use case. Thanks all for attending Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Ancor Gonzalez Sosa
-
josef Reidinger
-
Martin Vidner