Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make LinkParser extensible.
See original GitHub issueWith #1022 we now have a better default parser and user is able to provide their own parser.
But the LWM2M spec defines some specific grammar for its Attributes. This looks like some kind of link-extension.
So it seems that DefaultLinkParser/LinkParser should be extensible to allow to parse this kind of LinkExtention.
Ideally, Link class and Parser should not know about Attribute concept which is a pure LWM2M concept but I guess this is OK if AttributeModel contains a kind of LinkExtensionParser.
Implementing this will probably come with solving some raised issues like :
- drop the “splitting first” parsing. (more details here and here)
- better responsability handling about quoted sting/ excaping char / uri normalization (more details)
(Bonus question: Not clear to me but Link Parsing is also related to #1042 which I didn’t think too much for now)
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No problem. For the next time :
Thx a lot @Michal-Wadowski for you help 🙏