NASA-AMMOS / NASA-AMMOS/plandev

Add @NoParameters annotation for activity type classes

Open
#1,706 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
Java
Stars
128
Forks
33
Avg merge
1d 17h
Merged PRs (30d)
12

Description

Checked for duplicates

Yes - I've already checked

Alternatives considered

No - I haven't considered

Related problems

I'm frustrated when I get a compile error when I don't annotate any actvity type class fields as @Export.Parameter.

For activity type definitions, I often have fields for the class that I don't annotate as @Parameter. If no fields are annotated as @Parameter, the annotation processor considers all fields as parameters, which is a nice feature, but in some cases I want no parameters even though I have fields. Often, I have fields for which I don't have mappers and don't care/want to expose them as parameters, so I get an compile error.

Describe the feature request

I want something like a @NoParameters annotation for the class to prevent it from automatically creating the parameters for all of the fields. I do like the default to be to create the Parameters automatically, so I don't want to change that, especially since it would be a breaking change.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Java annotation processor for activity type definitions and the handling of @Export.Parameter. Trace how it treats classes with no annotated fields, then define the desired @NoParameters behavior and verify that fields remain excluded from generated parameters when the annotation is present.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.