Instantiating Condition

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java, spring
Domain
backend

Research direction

Start by reading the RequiresCondition extension and the current conditionClass.getConstructor().newInstance() path mentioned in the issue. Investigate how conditions could be managed as CDI or Spring beans and how request-scoped context would be accessed; the work is done when the instantiation and request-context behavior has a clear, agreed design and implementation scope.

Written by the indexing model from the issue text.

Description

I found this in the RequiresCondition extension.

conditionClass.getConstructor().newInstance();

In Spring, Condition can be defined as a bean and can evaluate the environment, properties, bean existence, etc., before instantiating a bean.

In addition, for example, when in an HTTP request scope, if the payment method (PAYPAL or STRIPE in the example) is selected in the browser and passed to the request, how should we handle it within that scope?

Here, the condition may require a context concept that is bound to the execution context.

Dominant language
Java
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.