Support string parameter 'canonicalName' for @Connect annotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Hi.
I'm some sort of migration from raw GWT to Vaadin plus my GWT widgets. I used last GWT maven plugin, and my project structure was like:
- root module
- client module
- server module
- shared module
I wanna save this structure (more maven ideology structure, and more clear code references inside projects).
But @Connect required hard reference to server code via Class<? extends Connector> value()
I patched code by adding parameter
String canonicalName() default ""
to @Connect.
But, it's provide a problem - value() is not required, and user can place @Connect without parameters, and need compiler check (added in my fork).
If it's acceptable - I can create pull requred from my fork.
Maybe provide another annotation?
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the @Connect annotation and the compiler validation mentioned in the issue. Determine how a string canonicalName should coexist with value(), including the required-parameter check; done means the annotation supports the requested module separation and rejects invalid usage consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100