Implement support for Parcels lib
See original GitHub issueParcels lib:
compile 'org.parceler:parceler-api:1.1.5'
apt 'org.parceler:parceler:1.1.5'
For example this lib:
compile 'com.hannesdorfmann.fragmentargs:annotation:3.0.2'
apt 'com.hannesdorfmann.fragmentargs:processor:3.0.2'
compile 'com.hannesdorfmann.fragmentargs:bundler-parceler:2.1.2'
Supports the parceler lib like this:
@Arg(bundler = ParcelerArgsBundler.class) public AnyItem item;
Add please support of lib parceler
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Building a library with Parcel
A getting started guide walking through how to setup a library with Parcel, including output of an ES module, CommonJS, and TypeScript definitions....
Read more >Parcel - Android Developers
You can use the direct methods writeParcelable(android.os. ... Retrieve a new Parcel object from the pool for use with a specific binder.
Read more >Solved: library copy to /opt/cloudera/parcels/CDH/lib/hado...
I am very new to hadoop eco system . Please somebody help me to file(external jar from my local system) copy to all...
Read more >Standard library - Go Packages
Package bufio implements buffered I/O. It wraps an io.Reader or io.Writer object, creating another object (Reader or Writer) that also implements the interface ......
Read more >Developing packages & plugins - Flutter documentation
Federated plugins are a way of splitting support for different platforms into separate packages. So, a federated plugin can use one package for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@PingForward please check out version 0.70-beta.1 Changes to apply:
Please let me know if everything is ok.
Why you choose this way? I mean why you define ParcelarArgConverter.class as one global config for all activties and fragments? Why not to use it for every specified argument? This way give much more flexibility to the user @Arg(bundler = ParcelerArgsBundler.class)